If you don't want to risk data loss, you need to correct that at the source (e.g. Note that the backup size does not include empty pages, but when you actually perform the restore, the data and log files will be over 200 GB, because it has to restore exactly what the source system had (including a 200+ GB log file, regardless of how full it was). Oh BTW, I am on SQL Server 2008 R2 Express. How can I bypass that ? It's a bit difficult to get a backup, so if I can resolve my problem without having to return on the production server, it would be great. So, if I understand correctly, restore checks that I have enough space to restore the "theorical" size of the log file before proceeding, disregarding the actual log file size ? The column BackupSizeInBytes returns 6,259,736,576 and 0. It asks for 227,891,019,776 bytes, which is absolutely crazy, and almost as big as my whole hard drive.Īs found on other sites, I tried RESTORE FILELISTONLY FROM DISK = 'backupfile.bak'. It fails with a message like : : insufficient disk space. I try to restore the backup on my SQL Express local server. It's a "light" backup of the original (with the log tables purged), which is about 14Gb.
0 Comments
Leave a Reply. |