Your task is unusual and actually not that easy as you have to consider 2 issues: timing & retention
1. Timing
=======
Honestly - before i would setup a specific schedule, i would add the clients to 3 disabled groups and prepare an appropriate savegrp job command which will be started by cron/task scheduler. The second is pretty comfortable in setting the jobs your're takling about.
The command itself should read like : savegrp -l full -w "6 months" -e "6 months" -G
2. Retention
=========
If you backup to tape, you should send a backup with a different retention policy to a different pool. Unfortunately, you cannot specify a pool along with the savegrp command.
But you could also use a single schedule (full_on_fridays) and later adjust retention time by running a script which will then stage the save sets with longer retention time to another pool (nsrstage -y "retention_time" -b pool -S ssid) .
Yes, external scheduling probably would do the trick, but I'd much rather let NetWorker deal with everything in the one place.
As for separate pools, NW would pick up this information from the group - we have the backups configured with the retention against the client and pool against the group (i.e. we'll have three clients all told in three groups - one for the Daily [month retention] group, one for the Monthly [six monthly retention] group and one for the Six-Monthly [six year retention] group).
Whilst we could run a staging process after the backup, I think that just complicates matters - I like to keep things as simple and straightforward as possible .
I did think my request was a bit "out there" so unless anyone comes up with a simple way to do things, I think I'll just manually add overrides to the schedules.
(I think this version of NetWorker knows dates up to 2038, so it shouldn't take me long to go through three schedules for the next 25 years, should it? )
bingo.1
2.4K Posts
0
February 22nd, 2013 11:00
Your task is unusual and actually not that easy as you have to consider 2 issues: timing & retention
1. Timing
=======
Honestly - before i would setup a specific schedule, i would add the clients to 3 disabled groups and prepare an appropriate savegrp job command which will be started by cron/task scheduler. The second is pretty comfortable in setting the jobs your're takling about.
The command itself should read like : savegrp -l full -w "6 months" -e "6 months" -G
2. Retention
=========
If you backup to tape, you should send a backup with a different retention policy to a different pool. Unfortunately, you cannot specify a pool along with the savegrp command.
But you could also use a single schedule (full_on_fridays) and later adjust retention time by running a script which will then stage the save sets with longer retention time to another pool (nsrstage -y "retention_time" -b pool -S ssid) .
Brian91_4544b4
71 Posts
0
February 25th, 2013 02:00
Thanks for the reply, Bingo.
Yes, external scheduling probably would do the trick, but I'd much rather let NetWorker deal with everything in the one place.
As for separate pools, NW would pick up this information from the group - we have the backups configured with the retention against the client and pool against the group (i.e. we'll have three clients all told in three groups - one for the Daily [month retention] group, one for the Monthly [six monthly retention] group and one for the Six-Monthly [six year retention] group).
Whilst we could run a staging process after the backup, I think that just complicates matters - I like to keep things as simple and straightforward as possible
.
I did think my request was a bit "out there" so unless anyone comes up with a simple way to do things, I think I'll just manually add overrides to the schedules.
(I think this version of NetWorker knows dates up to 2038, so it shouldn't take me long to go through three schedules for the next 25 years, should it?
)
Brian