Policy Based Backups Need Automatic Feature
We have implemented and used your "policy based" backups. They seem to be cumbersome and have at least one major issue that reduces their value as a feature.
Perhaps we are missing something, but here is a sample scenario we run across:
- There are ten machines being backed up by a policy called "Monday Cycle".
- This policy does a complete backup on Monday using media set "Complete Backups." Other days it does a differential backup using media set "Differential Backups".
- Now two of the machines were off-line for some time time and miss a few "Complete Backups".
- The media for those two machines gets recycled since the retention period has passed.
- At this point we have no backup for those machines.
To avoid this, we can create a media set for each machine. That way any machines off-line will still have their latest backup and it would not be re-used.
But using a "policy" determines the media pool to use, that means we cannot use policy based backup unless we are positive that all machines are on-line and ready to be backed up.
Because of this limitation to your "policy" mechanism, we have folks checking backups everyday and re-running backups or finding the media to change to another pool to keep the media for missed machines.
You should be able to create a better way for this work.
For example, the "policies" could have "keywords/variables" that contain information about the current resource being processed. The variables could be use to select a media set unique to that machine.
Or maybe make changes to how media is managed during a re-cycle operation. If the resource in the media references a policy based backup and there is no newer backup then delay the recycle.
But the bottom line we see is the "policy" based backups have a high overhead and the value of this feature is limited.
Thanks, and if you have any suggestions on resolving this let us know.