Quite simple. Groups are scheduled by networker at time matching naming.
I try to move in groups clients to have backups completed before next time
increment (1h for eg).
Ex : If a group start at 18:00, I try the group to finish its task list before
18:45 for sample,
giving Networker time to "relax" a bit and properly complete all remaining
threads.
Next, I avoid all clients to take a full at same day. So, I create schedules
like F111111,
1F11111, 11F1111, 111F111, 1111F11, 11111F1 and 111111F for sample.
I assign schedules to spread Fulls over the week, not all the same workday.
Thanks to my business needs, if I take a full on Friday on some clients, I may
skip Sats,
giving more timeslot for a bigger client who run over multiple time block
Doing so, if you need to reschedule a client, just move it from group,
if you have a cluster with 2 big file services, take one member and 1 file
service
a day, the others the next day.
If you need to force a full for a specific intervention (like next sat, we
upgrade I need a full backup)
create a new sched for involved clients and overrule the calendar like "full
04/19/2012" without changing anything else
in your config.
Also, in retention, avoid name like "3 WEEKS" with retention period=WEEKS and
amount of period =3
If you need to change your retention, you will need to update all clients. If
not, you will have a retention
meaning "3 WEEKS" that may be set completely different (eg as "2 weeks"). Use
like "POLICY-BROWSE"
and "POLICY-RETENT" and "POLICY-CLRETENT" for sample to set your default browse
and
retention policies and if cloned savesets must have different retention than
original savesetid copies.
Just update 1 resource and you are done.
Give also a look at Advanced File devices. For small clients over the lan, it's
ideal.
You take your backups to a disk based device during the night and during the
day,
you move data to tape. This avoid tape fragmentation during backup and, when
you need to recover, you recover from continuous tape blocks, in other words,
faster !
HTH
TH
-----Message d'origine-----
De : EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] De
la part de Vygur
Envoyé : mardi 17 avril 2012 16:45
À : NETWORKER AT LISTSERV.TEMPLE DOT EDU
Objet : [Networker] Best Practice in naming Networker Groups?
Thanks Thierry, that was very helpful!! How do you manage your load balance
and schedule your backups?
+----------------------------------------------------------------------
|This was sent by tigurius AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
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
|
