Finer granularity for netbackup
Created: 20 Jul 2010 | Updated: 21 Sep 2010 | 2 comments
Status:
Implemented
It would be nice to have finer control on what runs and when...
-the ability to deactivate a client within a policy, instead I resort to renaming it to some unresolvable hostname
- the ability for netbackup to NOT try and backfill 'missing' backups. This is annoying...if I add in a new client to a policy with multiple schedules, instead of just carrying on it has the genius idea of backfilling the backups it hasnt done in the past, per schedule, so you end up running a yearly , a monthly , a weekly, whereas I'd just like it to just follow the calendar going forward and forget about what it hasnt done.
Idea Filed Under:
Comments 2 Comments • Jump to latest comment
I believe this has already been deployed in the release of netbackup 7.01 except that it appears in the client attributes tab on the master servers host properties.
The down side is that you have no way of telling in the policy if its disabled (coloured red or greyed out or something!) and it isn't specific for a particular policy - it deactivates all backups for that client.
This is in 7.0.1 and agreed that we need to expand the reporting/monitoring and controls around it.
Sr. Product Manager, NetBackup
Symantec
Would you like to reply?
Login or Register to post your comment.