Comments
4 comments
-
SQL Backup does not require nor create a temporary file while it is backing up a database. SQL Server passes it the backup data, it compresses it, then writes it out to disk immediately.
-
thanks!
-
Is the reverse true as well when doing the restore?
-
Yes, there are no temporary files generated during a restore as well.
Add comment
Please sign in to leave a comment.
Currently, my MS SQL database is 155gigs. The drive capacity is 350gigs.
After the DB is backed up with compression, it's 30 gigs. And I keep 2 days worth of backups on disk (goes to tape at night). So that's 155+60=215gigs worth of space being used. That leaves around 135-145 gigs of free space.
My question is, while Red-Gate SQL Backup is RUNNING, how much "extra" free disk space do I need for the backup to work?
I always used rule of thumb: you need at least 3x the amount of the size of the database (for total drive capacity), to account for the actual database, the resulting backup file, and the temporary space the backup needs while it's creating the backup file.
But I'm not sure if this is true with Red-Gate. Can anyone advise me on this?
Thanks!
Dave