Punitsingh Suryawanshi wrote:
If your clients already have default schedule why are you overriding it with
group schedule? You can remove group schedule (leave it blank) create a
"full" schedule with daily level as full, assign full schedule to these two
clients, start backup group and revert the changes.
Ah, yes, of course. NOW I see what you're saying. I usually just always
assign each group to a specific schedule and allow that to override the
client's 'Default' schedule, but in this case, temporarily changing the
group's schedule to a blank forces the client's schedule to be used, so
I did what you said, and a 'savegrp -n group_name' reports exactly what
I wanted. It should run just that way when it kicks off later tonight.
The only caveat is to ensure that the Default schedule is correct for
the other clients in the group, and it is.
I'll reset everything tomorrow.
Thanks for your response. The solution was so obvious that I overlooked
it. Sheesh!
George
Regards,
-Punit
On Thu, Jan 6, 2011 at 4:51 AM, George Sinclair <George.Sinclair AT noaa DOT
gov>wrote:
Hi,
Is there a slick way to force NetWorker to run a level full for two clients
in the same group without forcing it to run fulls on all the clients in that
group but still allow the other clients to run their normally scheduled
backups?
Here are the possible solutions that occur to me:
1. On the server, run 'savegrp -l full group_name -c client1 -c client2'
Yes, of course, this will work, but I'd really prefer to have all the
clients run, but only those two run fulls; the others would run whatever the
group schedule normally calls for (in this case, an incremental).
This is because when I run 'mminfo', I'd like to see all the clients
reported. I guess I could run the above command a second time on the other
clients, but specify '-l incr' ?
2. Create a temporary group, change each of the two client's configuration
to now be a member of that second group, set its schedule for a full and
then run that group.
Seems like a long winded version of solution 1, and the other clients in
the original group still would have to be separately launched, and 'mminfo'
would not report them all as being from the same group.
3. All the clients in the group have the 'Default' schedule. The group has
a custom defined schedule. If I create a new schedule, set it to a full and
then change those two client's schedules from 'Default' to the new schedule,
will that override the group's schedule, or will NW still use the group's
schedule?
If it will override the group's schedule then maybe this would be best?
suspect it will not override it?
4. Can I change the backup command field to 'save -l full' for those two
client resources and then clear it when the backups are done???
My experience with this when running 'save' from the client is that it
ignores the '-l' option and runs an adhoc backup. I want 'mminfo' to report
a level of 'full'. BUT, since the backup is not being manually initiated
from the client then maybe this would force a level full to run on all the
save sets for that client resource? Or would it still act like it was being
run from the client?
Maybe there's some other solution?
Thanks.
George
--
George Sinclair
Voice: (301) 713-3284 x210
- The preceding message is personal and does not reflect any official or
unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
"signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
--
George Sinclair
Voice: (301) 713-3284 x210
- The preceding message is personal and does not reflect any official or
unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
