Comments
1 comment
-
Thank you for your post into the forum.
I suspect that you are selecting the destination database you are choosing the option to overwrite an existing database, I am correct? If the answer is yes, then you have encounter a known bug where SQL Backup when restoring the FULL_SEED backup, will modify the file location paths for the mdf and ldf files to the default SQL Server path.
To work around this problem, when selecting the destination database can you please select the option to create a new database. You will then be able to configure the file location paths for the mdf and ldf file to be on another drive that has sufficient free space.
Many Thanks
Eddie
Add comment
Please sign in to leave a comment.
Any ideas how I can get SQL Backup to use the free space on another drive rather then using C, or get it to process in smaller chunks so that it does not need the full 19GB?
Cheers...Steve