Unsolved
This post is more than 5 years old
47 Posts
0
3602
How to specify start order of clients in one savegroup
Hello,
I am looking for the possibility to specify start order of clients in one savegroup…
Here an example:
Clients in savegroup ARC-BKP
- Mars (archiving server)
- Saturn (database server)
- Neptune (fail server)
Mars is using savepnpc command to put client server in backupmode, and the backup of Saturn and Neputune
should start once the Mars is in backup mode.
Mars should stay/wait in backup mode so long the backup of Saturn and Neptune is running.
Once the backup of these two serer is finished the postjob should be executed to end the backupmode of Mars server…
Any ided how to tell Neptune and Mars to wait for 2 min while the Mars is running) and then (Mars is in backupmode) to start backup???
Is there any way to set some kinds of sleep interval in backup command ???
Thanks&Regards.
TimQuan
1.2K Posts
1
February 8th, 2012 17:00
Hi,
In Administrator Guide:
The Priority attribute in the Client resource specifies the order in which clients are contacted for backup. The attribute can contain a value between 1 and 1,000. The lower the value, the higher the priority.
The client with the lowest value for the Priority attribute is placed at the top of the list to be contacted by the NetWorker server. If a value is not specified in the Priority attribute, the backup order is random.
While the Priority attribute specifies the order of client contact, many variables affect the order in which clients complete their backups, including these scenarios:
Note: The only way to guarantee that ClientA backs up before ClientB is to assign ClientA to a scheduled backup group that starts earlier than the group containing ClientB.
Regards,
Tim
vucko
47 Posts
0
February 13th, 2012 08:00
Hi,
Unfortunately, NW priority feature from Client resource doesn't help in this matter, because the used priority numbers are more some kind of relative value, and not times interval... I've tried to use that, giving to Mars priority value 1 and to other two servers 999 but when the savegroup starts, all three servers are starting backup together in same time..
We've solved this use with savepnpc command on all three clients, on both server in question (Neptune and Saturn) savepnpc starts prejob (wait 5 min before backup start)...
This solution is working fine, but there is still a problem to start backup of SQL Database with NW module for SQL, because of backup command (savepnpc), execution of nsrsqlsv command from prejob of savepnpc doesn’t work.
So that we are currently using only backup of SQL dump files. (not so fine solution because of point in time recovery and SQL transaction logs..)
Any idea how to predefine prejob of savepnpc command so that this process after wait time start nsrsqlsv service on client side?
Thannks & Regards
ble1
14.3K Posts
1
April 25th, 2012 01:00
You should be able to run all from single script... basically, you would call one single master script which calls subsequent ones... though I do not understand why such approach is needed in the first place.
DavidHampson-rY
294 Posts
1
April 25th, 2012 08:00
The most obvious solution would be to assign Saturn and Neptune to a new group configured to start two minutes after the start time of the group assigned to Mars.
Lucky85
173 Posts
0
April 25th, 2012 23:00
There is priority option in client properties, there you can setup priority of client which gives order how the clients will be called during savegrp startup…
Thierry101
326 Posts
0
August 21st, 2013 21:00
We have similar situation...but all clients in the group cannot be separated out using different groups for EV backup consistency...there is a need for ndmp backup start first due to streams limitation...looks like the priority is not working as expected?
NW7.6.3
thanks
Brian91_4544b4
71 Posts
0
August 22nd, 2013 01:00
Hi Thierry
Could you set your NDMP client priority to 1 and set the savegroup parallelism value to match the number of NDMP streams (or a lower number if you have several)? That way, your NDMP backup should start first and only when all streams have been started and/or finished will the others kick in.
Brian