I have just implemented a different approach to backing up 2 very large volumes on my main file and print server. The "D" and "E" drives contain roughly 750 gigs each, and the full backup on Fridays was brining the server down to a crawl. I wrote a script that creates a snapshot of the drives on the storage array, mounts them to a dedicated backup server (just a file system client currently, but soon to be a dedicated 64bit media agent), runs the backup and finally dismounts the snapshot volume. Everything is working great and the speed is nearly 3 times as fast. I ran a full backup, with the snapshot, on Tuesday, 2 incrementals on Wednesday, and incremental on Thursday and 1 last night before the synthetic full. I was surprised to see this morning that the size of the synthetic full was only 205.63 gigs as opposed to the size of the true full backup from Tuesday which was 722.04 gigs. Does this make sense? I figured they would be roughly the same size or at least a lot closer than they appear to be.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Size of synthetic full backups
- Thread starter JG5
- Start date
- Thread starter
- #3
I figured it was indeed wrong. Now I'm questioning all of my synthetic fulls from other systems as well. One of the subclients from the client in question appeared to be correct, but the other was not as stated earlier. Guess I'll see what updates are available and then play the log file shuffle with CV support.
- Status
Similar threads
- Locked
- Question