April 29, 2014 at 5:07 am
When doing a differential backup, is it better to save to a new file or use the full backup file?
In general what resources get used during a differential backup and does it affect reads and writes to the database?
Thank you, djj
April 29, 2014 at 5:11 am
All backups, regardless of their type, should go to their own individual file, preferably stamped with the date and time of the backup.
Differential backup, just like a full, is an IO-intensive operation, so the IO subsystem will be under load during the backup.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 29, 2014 at 5:13 am
save to a new file. Makes restore process easier.
Backups are i/o intensive, so backup to a different drive. CPU will also increase if compression is used. Use of the database can continue without interruption whilst the backup takes place
---------------------------------------------------------------------
April 29, 2014 at 5:15 am
Thanks. Since the MS default is to append I did not know, even though I always do the full backups into separate files.
We have grown and I was wondering about stating a differential backup, however we need to get better hardware as we are currently having I/O stress.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply