Deactivate by client
Updated: 31 Aug 2010 | 24 comments
Status:
Implemented
This has been mentioned before, probably in the previous incarnation of the NetBackup forum, but now we have 'Ideas', so:
"We do on occasion have the need to suspend NetBackup activity for particular clients (upgrade, maintenance etc etc) & it would be very useful to have the ability to suspend/deactivate scheduled backups on a per client basis. (Or even a per client/per policy basis if changes are being made to a particular area on a particular client).
Currently, our only or easiest option is to remove said client from each & every policy in which it resides."
idea Filed Under:
Comments
Yes Andy ! It will be helpful more :)
My Vote for this !
Thanks, Karthikeyan Sundaram.
Totally agree
Andy, I agree on this. Make it possible to deactivate the client. Sometimes a client is down for a reason. When it is deactivated, the NetBackup policy should exclude it from the scheduled run.
report
There should also be a report of clients that have been deactivated for reminding the Netbackup operators to reactivate.
Bob Stump VERITAS - "Ain't it the truth?" Incorrigible punster -- Do not incorrige
.
To go along with Bob's idea - When viewing 'All Policies' in the NB Admin Console, the policies should have a different icon or color to let you know some of the clients are disabled within a policy. Similar to the way disabled policies show up now.
Very good point Bob.
:)
Regards Andy
"It's not too late to panic ..."
Similar in sense to Deactivate Media Server - kind of.
I agree too. OK you can deactivate a media server, this still doesn't stop the policy execution scheduler from running a policy that includes this media server as a client. But why not deactivate client. Good addition.
I remember this was discussed a couple of years ago in the previous forum - to exclude a client from a policy - temporarily.
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Yes from me
Oh yes, save those red X's overnight
NBU v7.1.0.1 Master and Media servers on RHEL 5 & Win2008; SAN based LTO 3 and 4 tape libraries.
Linux, Solaris, Windows and OpenVMS clients.
PureDisk, SLP, VMware, Oracle, SQL/Server and Exchange agents
VBR and OpsCenter
I strongly agree
I strongly agree !!!!!!!!!!!!!!!!!!!!!!!!
Thanks & Regards,
Venki
Dont forget to Vote for + if you think suggestion is good, and mark as solution if it has resolved your problem.
agree....but...
While I agree with this in concept, there is a work-around for this of sorts. That is if you have one client per policy, then you simply disable the policy and re-enable it when you are ready. This has been mentioned in backupcentral.com by Curtis Preston.
Remember.....Google is your friend!
Yeah, read all that.
and very good arguments for both 'methods', but a little simple functionality would make administering the many clients/policy set-up that much easier! ;)
Regards Andy
"It's not too late to panic ..."
Do it Symantec !!!!
Please !!!!!!
Deactivate by client
Can anyone post a status about this topic? Will it come with NetBackup 7.0?
Best regards!
Peter
You can disable all backups
You can disable all backups on a Windows client by stopping the NetBackup Client Service on it. You will get a failure status (probably 58 - can't connect to client), but a failed backup is better than a silently missed one.
For managing policy settings, backup selections and client lists, you can use NetBackup commands with scripts.
How's the "Review" going?
How's the "Review" going?
Regards Andy
"It's not too late to panic ..."
I HOPE my interpretation of
I HOPE my interpretation of this feature in 7.0.1 is correct:
http://seer.entsupport.symantec.com/docs/356785.htm
The marquee features of NetBackup 7.0.1 include:
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
NBU 7.0.1
Yes, this feature has been incorporated into the NBU 7.0.1 release. Check out the official announcement on "NBU Twitter" feed for more details.
Thanks for listening to us
Now implemented!
this feature is now implemented and released in NBU 7.0.1 which went GA today! It is called "Client Offline" in the documentation.
Thank you to all of you who voted and commented on this feature!
Keep the great ideas coming.
Stephen Stange
When anyone tries it & advise if
"it does exactly as it says on the tin"?
Might as well have a bit of feedback as to how these ideas turn out!
Regards Andy
"It's not too late to panic ..."
Seems to!
Seems to!
I disabled a couple of clients and quite simply the backups didn't get scheduled. One was even a Windows client with both normal ALL_LOCAL_DRIVE and even an SQL/Server DB backup policy. Neither polciies got scheduled.
I then undisabled them and a few minutes latar; jobs got scheduled.
My only complaint; the "slow" mechanism to disable/enable via the Master Server Client Attributes setup. I always find the "apply" bit of this very slow.
That all said, it works for me. Thanks Symantec.
NBU v7.1.0.1 Master and Media servers on RHEL 5 & Win2008; SAN based LTO 3 and 4 tape libraries.
Linux, Solaris, Windows and OpenVMS clients.
PureDisk, SLP, VMware, Oracle, SQL/Server and Exchange agents
VBR and OpsCenter
Client Offline Documentation
Can anyone point me in the direction to the documentation on how to use the offline feature I cannot seem to find it in the Admin guide.
Have a look in the Admin Guide (starting with 7.0.1):
e.g.
Symantec NetBackup(tm) 7.0.1 Administrator's Guide for UNIX and Linux, Volume I
http://www.symantec.com/business/support/index?pag...
page 85
The client offline feature is within the Master Server Properties/Client Attributes/General Tab.
Regards Andy
"It's not too late to panic ..."
Solaris master
That looks to be for a windows master. Is this option available for a Solaris master?
What makes you think that?
The Admin Guide I quoted above was for UNIX......
Regards Andy
"It's not too late to panic ..."
Would you like to reply?
Login or Register to post your comment.