Help make SSR Smarter - Manage Backup Destination & Limit Number of Recovery Points Saved

Is anyone else struggling to coerce SSR 2013 R2 on Windows Server 2012 R2 to properly manage available backup disk space?

SSR 2013 R2 offers two features: Manage Backup Destination, Settings, Monitor disk space usage for backup storage, and Define Backup Wizard, Options, Limit the number of recovery points saved, but neither of them appear to work.

Monitor disk space usage is unavailable (it's greyed out) for backup drives used with backup jobs configured for USB Disk Rotation.

Limit the number of recovery points saved is messy when used with USB Disk Rotation backup drives because the Limit is the total number of recovery points spread among all the backup drives, which is overly constrictive like a snake.

For example, SSR requires us to manually anticipate and continually verify that all the recover points will fit on every backup drive.  Additionally, the backup size better not increase, otherwise we have to manually decrease the Limit.  And, watch out if some other space hungry files are written to the backup drive (who hasn't used their backup drive to write a quick file!).

All this oversight and intervention is necessary when using the Limit function becasue SSR will NOT automatically delete the oldest backup, instead it will pop-up an insufficient space message and sit there waiting for response.  Meanwhile, days and weeks can pass with NO backup!  All of this simple disk space checking activity can be more easily and efficiently handled by SSR instead of requiring the attention of an administrator.

Thoughts?

3 Replies
Highlighted

Please post your ideas here:

Please post your ideas here: https://www-secure.symantec.com/connect/node/add/idea?add_context=711

Hopefully they'll get picked up by product management.

Highlighted

All this oversight and

All this oversight and intervention is necessary when using the Limit function becasue SSR will NOT automatically delete the oldest backup, instead it will pop-up an insufficient space message and sit there waiting for response.

This sounds like something that should be investigated further. Have you opened a support case for this?

Highlighted

Any updates here?

Any updates here?