We have a Windows 2012 server that runs AD and Hyper-V with 2 VMs. Total disk space is 2TB. We have 5x 2TB USB disks that are rotated daily from Monday to Friday. Currently I have a scheduled task that fires off a batch file with the following in it:
wbadmin start backup -allcritical -systemstate -include:"c:" -backuptarget:E: -vssfull -quiet
WSB backup performance is currently set to "Normal backup performance".
The reason I went this route is because I had issues trying to get WSB to use all 5 drives in rotation through the GUI. Connecting all 5 drives at the same time when setting up the backup is just not feasible.
When I initially configured the backup it ran fine for the first 2 weeks whereby the backups would take about 16 hours to finish which was fine (starting at 6pm and finishing around 10am the next day). For some reason now the backups are taking around 26 hours to finish which I don't understand as the size of the data hasn't changed much.
I have now changed the performance to "Faster backup performance" but I'm not sure if it will work with the drives being changed daily as the comparison of say Monday's snapshot on the server will be different to the backed up data on Tuesday's drive. Or alternatively, if the comparison of changes is only done on the server and the differences are copied across, will it cause issues when trying to restore the backup?
Basically what I need to achieve is:
- The RPO is 1 day so that in the event of catastrophic failure we need to be able to restore the server completely to the previous day (obviously within reason of when the catastrophe occurred).
- We need 5 days worth of backups from Monday to Friday.
- Each drive is swapped out daily to be taken off site.
If I need to look at doing a full backup every weekend and leaving a single drive connected for the week for "incrementals" then I can discuss that with the managers but that would change the RPO to the previous week instead of the previous day if the building burns down for example.
wbadmin start backup -allcritical -systemstate -include:"c:" -backuptarget:E: -vssfull -quiet
WSB backup performance is currently set to "Normal backup performance".
The reason I went this route is because I had issues trying to get WSB to use all 5 drives in rotation through the GUI. Connecting all 5 drives at the same time when setting up the backup is just not feasible.
When I initially configured the backup it ran fine for the first 2 weeks whereby the backups would take about 16 hours to finish which was fine (starting at 6pm and finishing around 10am the next day). For some reason now the backups are taking around 26 hours to finish which I don't understand as the size of the data hasn't changed much.
I have now changed the performance to "Faster backup performance" but I'm not sure if it will work with the drives being changed daily as the comparison of say Monday's snapshot on the server will be different to the backed up data on Tuesday's drive. Or alternatively, if the comparison of changes is only done on the server and the differences are copied across, will it cause issues when trying to restore the backup?
Basically what I need to achieve is:
- The RPO is 1 day so that in the event of catastrophic failure we need to be able to restore the server completely to the previous day (obviously within reason of when the catastrophe occurred).
- We need 5 days worth of backups from Monday to Friday.
- Each drive is swapped out daily to be taken off site.
If I need to look at doing a full backup every weekend and leaving a single drive connected for the week for "incrementals" then I can discuss that with the managers but that would change the RPO to the previous week instead of the previous day if the building burns down for example.