Backing up SQL

  • We need to back up our databses in order to create a larger F drive on out SQL server. Does anyone know if it is ok, or recommended to simply backup the MDF and LDF files? In other words, we are going to copy the MDF and LDF files off the machine to a share on the network - then add a drive and extend the F drive onto that new drive. We are copying all the files as a backup in case the "extension" does not work for some reason. Anyone know if this is okay? Or if we should backup instead? OR?

    Thanks!

    JP

  • Is there any software installed on the F drive? If so, you have some additional things to think about. Are you going to delete the existing partition and rebuild it with the additional drive? Or are you going to just extend the partition? If you extend the partition, the integrity of the files should not be compromised. If you delete the current partition, you will need to recreate the directory structure and replace any files needed by SQL. It is always a good idea to have a good backup prior to making any changes to your server. Is there a reason you have data and log files on the same drive? This is normally bad for performance.

    Brian

  • If you are shutting down SQL Server anyways and planning on moving the files (which it appears you are doing), then yes. Detach all the databases. Copy (or just move) the .mdf and .ldf files. Put them into their new location. Then attach them. If you moved them to a new directory (or drive) you will need to identify that when you attach them.

    -SQLBill

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply