Idea ID 2798038
In our environment we often see clients taken offline for extended periods. Each day the backups for these clients fail, causing additional load for the backup administrators who investigate / review these failures. The only way to currently address this issue, is to remove the client from backups, then re-add the client when the client is put back online. This can be an extensive process depending on the complexity of the backup (i.e. number of protected paths/objects, filters / exclusions, etc.)
Our environment is large, so it is not practical to give each client a standalone job that can be enabled / disabled.
It would be nice if the backup for individual clients could be enabled / disabled as needed within the backup specification. The backup specification would then run as scheduled but backup only those clients that are enabled. No backup would be attempted on disabled clients, and no errors would be generated for clients that are offline.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.