02-15-2012 08:21 AM
Hi All,
Just need some help if possible.
We have 50 clients that will going to decommission and I want to do monthly backup for all those servers. Is there any way I can automate it or have to do cherry pick in the policies as there are lot of policies in the environment. I am also thinking of creating a new policy all together and dump these 50 servers in one go but is there any way I can put the jobs in other policies on hold or delete them all.
In short,I am just looking for some kind of command or script which can put these 50 clients on HOLD or remove them from policies.
Environment: Windows 2003, Master and Media on 6.5
thanks for helping!
Regards
.
Solved! Go to Solution.
02-15-2012 08:40 AM
Good news: Clients can be put on hold.
Bad news: Not on version 6.5
'Offline/Suspend Client' was introduced in NBU 7.0.1. Extract from 7.0.1 Release Notes:
About NetBackup client offering
The new Offline option in the Client Attributes properties lets administrators take
individual clients offline to make the clients unavailable for backups. When a
client is offline, no backup status is listed for the client.
That is useful in a number of situations. For example, in the event of planned
maintenance, you can take the client systems offline to avoid the unnecessary
errors that then need to be investigated. This option can also be used to anticipate
new clients in the system. The clients can be listed in policies but configured as
offline until they are in place and ready to be used.
In addition, you can specify a period of time that the client is automatically enabled
again. That prevents users from forgetting about the clients that were in an offline
state.
Hopefully this is enough motivation to upgrade?
If you need more motivation: NBU 6.x will be EOSL later this year...
02-15-2012 08:40 AM
Good news: Clients can be put on hold.
Bad news: Not on version 6.5
'Offline/Suspend Client' was introduced in NBU 7.0.1. Extract from 7.0.1 Release Notes:
About NetBackup client offering
The new Offline option in the Client Attributes properties lets administrators take
individual clients offline to make the clients unavailable for backups. When a
client is offline, no backup status is listed for the client.
That is useful in a number of situations. For example, in the event of planned
maintenance, you can take the client systems offline to avoid the unnecessary
errors that then need to be investigated. This option can also be used to anticipate
new clients in the system. The clients can be listed in policies but configured as
offline until they are in place and ready to be used.
In addition, you can specify a period of time that the client is automatically enabled
again. That prevents users from forgetting about the clients that were in an offline
state.
Hopefully this is enough motivation to upgrade?
If you need more motivation: NBU 6.x will be EOSL later this year...
02-15-2012 08:51 AM
Excellent advice from Marianne as always!
So for what you are doing I would reccomend you go with a decomission policy - a one off with a suitable retention period and drop the servers in it as you need to
As you only want to back them up once I would be inclined to either run it manually or set a schedule and remove the client from the policy once it has had its "final" backup
02-15-2012 11:46 AM
One last question, is there any way i can remove those 50 clients in one go without going manually to each and every policy, i mean with some command or anything?
02-15-2012 12:14 PM
If the policy names are known, you can delete clients with bpplclients.
Extract from Commands manual:
bpplclients policy_name -delete host_name ...
Delete one or more clients from the policy. Up to 20 clients can be deleted at
a time. The clients are provided as a space-delimited list of host names.