Is that 300 clients per server or 300 clients per 30 servers?
What is wrong with monitoring? Do you have NMC? Stopping groups could be a workaround, but what you should focus on is why are they hanging and fix that. Do these clients have backup window? Do yo use inactivity timeout (I believe that should work with hanged sessions).
Nevertheless, there was an idea to implement field for when the group is running more than the value defined it would be stopped. I think that was not implemented in 7.3, but I'm not 100% certain.
300 clients per 30 servers, in every site we have ~5-15 servers to backup. There are 30 sites and around 300 servers. Yes I have central NMC for all servers and NMC on every backup server per site (30 NMC on sites and + 1 NMC central). Yes I can stop groups manualy but how to find that somewhere between those 30 servers there still running groups? Clients have backup window at night from 21:00 to 6:00 every night. Inactivity timeout is by default 30 on all groups.
"Nevertheless, there was an idea to implement field for when the group is running more than the value defined it would be stopped. I think that was not implemented in 7.3, but I'm not 100% certain." And I was talking exactly about this option Its sad that it is not implemented... the same as authorization to NMC using AD groups
Well, in the morning when you come to your desk, you could check if any of the groups is running. Given that backup windows is until 6AM they should not. If yes - just check in what status backup is, why is it taking that long to finish and take corrective actions.
If I would need to maintain 30 servers I would certainly run a script which would gather all the data I need or require for to see in the morning if everything is all right.
if you need to start an application that is shut down via savepnpc, then use the timeout setting in the /nsr/res/ .res file
if you really want to stop the entire backup process, then you can use the nsradmin in a crontab for unix or a scheduled task in windows. in unix, i have this little nsradmin script that stops the backup:
DavidHampson
2 Intern
•
1.1K Posts
0
April 26th, 2006 03:00
ble1
4 Operator
•
14.4K Posts
0
April 26th, 2006 03:00
What is wrong with monitoring? Do you have NMC? Stopping groups could be a workaround, but what you should focus on is why are they hanging and fix that. Do these clients have backup window? Do yo use inactivity timeout (I believe that should work with hanged sessions).
Nevertheless, there was an idea to implement field for when the group is running more than the value defined it would be stopped. I think that was not implemented in 7.3, but I'm not 100% certain.
mdabasinskas
72 Posts
0
April 26th, 2006 03:00
Yes I have central NMC for all servers and NMC on every backup server per site (30 NMC on sites and + 1 NMC central). Yes I can stop groups manualy but how to find that somewhere between those 30 servers there still running groups? Clients have backup window at night from 21:00 to 6:00 every night.
Inactivity timeout is by default 30 on all groups.
"Nevertheless, there was an idea to implement field for when the group is running more than the value defined it would be stopped. I think that was not implemented in 7.3, but I'm not 100% certain."
And I was talking exactly about this option
ble1
4 Operator
•
14.4K Posts
0
April 26th, 2006 05:00
If I would need to maintain 30 servers I would certainly run a script which would gather all the data I need or require for to see in the morning if everything is all right.
techsup2
34 Posts
0
April 26th, 2006 18:00
if you really want to stop the entire backup process, then you can use the nsradmin in a crontab for unix or a scheduled task in windows. in unix, i have this little nsradmin script that stops the backup:
#!/bin/sh
NSR_SERVER_HOST=backupserver
NSR_GROUP_NAME=${1}
nsradmin -s ${NSR_SERVER_HOST} -i - << EOF
. type: nsr group;
name: ${NSR_GROUP_NAME}
option hidden
update stop now: true
EOF
the 1. is a . actually
Message was edited by: techsup
Message was edited by: techsup