February 18, 2012 at 2:45 am
I have two similar databases on the same server. Each one is about 1.5 TB and each is partitioned over about 100 files/file groups. When I back them up, I use the same script for both, a stored procedure with parameters for database and backup path.
The first one starts by creating a 0 byte backup file that grows until it is done and ends up with a compressed file that is about 100 GB. The second one starts by immediately creating a 300+ GB backup file. It runs until it is done and then compresses the file, which ends up to be about 100 GB.
My question is, "what causes the different types of file growth?". And of course, the first scenario is preferable, because for the second, I need to have 200 GB of space available that in the end is unused, but if it is not available, the backup fails.
Am I missing some setting?
February 18, 2012 at 9:34 am
jcoffey-872763 (2/18/2012)
I have two similar databases on the same server. Each one is about 1.5 TB and each is partitioned over about 100 files/file groups. When I back them up, I use the same script for both, a stored procedure with parameters for database and backup path.The first one starts by creating a 0 byte backup file that grows until it is done and ends up with a compressed file that is about 100 GB. The second one starts by immediately creating a 300+ GB backup file. It runs until it is done and then compresses the file, which ends up to be about 100 GB.
My question is, "what causes the different types of file growth?". And of course, the first scenario is preferable, because for the second, I need to have 200 GB of space available that in the end is unused, but if it is not available, the backup fails.
Am I missing some setting?
Could you please post the script?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply