Networker

Re: [Networker] Schedule overrides

2009-01-14 17:41:24
Subject: Re: [Networker] Schedule overrides
From: Fazil Saiyed <Fazil.Saiyed AT ANIXTER DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 14 Jan 2009 16:38:17 -0600
Hello,
It may be more simpler to use cmd line backup to start a group with level 
and pool argument, atleast you will not need to make sure the client 
exists in two separate group and manage them.
Having a simple Tape cleanup script might assist you in cleaning up 
expired tapes as well.
HTH



Jóhannes Karl Karlsson <johannes.karlsson AT SKYRR DOT IS> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
01/14/2009 04:28 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Jóhannes Karl Karlsson              <johannes.karlsson AT SKYRR DOT IS>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: Schedule overrides






So group schedule overrides client schedules? 

I think it would be clever, if that was only true, if the clients used the 
default schedule. But if the clients used a custom schedule, and that 
would override the group schedule, offers a little more flexibility. 

But I find it interesting that you're using client schedules as a rule. I 
like this idea of group schedules, it keep things simple. All the clients 
in every group do Full backups at the same day. 

In my case I have a seperate Incremental group and a Full group for every 
day. The inc group does not run when the Full group does it's Full (which 
otherwise has skip).  With this schema we do Full once a month, 
incremental every day, and Level backup every weekend . By separating the 
Full backup from the inc and L9 backups with pools, we make most out of 
the space because the inc and L9 expires before the Full backups, thus 
freeing up tapes.

But it would be kind of interesting to know about other strategies.




-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Fazil Saiyed
Sent: 14. janúar 2009 21:16
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Schedule overrides

Hello,
You may need to move that client to another group, use cmd line backup or 
forgo using group schedule, personally, i prefer not using group schedule, 

that give me flexibility to use various schedule with clients  and still 
group the clients in a group, it all depends on what your environment is 
like and what you are trying to accomplish.
HTH



JK <johannes.karlsson AT SKYRR DOT IS> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
01/14/2009 03:02 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
JK <johannes.karlsson AT SKYRR DOT IS>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Schedule overrides






Hi.

We're using schedules configured on per group level, so all clients in the 


same group use the same schedule.

But is there a way to make an exception, and configure a schedule on a 
single client in a group, so that client uses different schedule than the 
other clients?

Johannes

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


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

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


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