Re: [Networker] Best Practice in naming Networker Groups?

My favorite ones :

To make diff between Prod, Dev and Acceptance env,
and to enable auto Cloning on full only :
<P/D/A/>_<TIME>_<FULL/DIFF>
Setting <TIME> as savegroup start time, has the advantage of
visual info about when group start. Create according needs.
ex P_1800_FULL,  D_0015_DIFF

<TIME>_<CONTENT>_<FULL/DIFF>
Setting <TIME> as savegroup start time, has the advantage of
visual info about when group start. Create according needs.
ex 1800_WININFRA_FULL.
Disadventage if you need to reschedule at 20:00 in way of 18:00,
you have to create a new group.

<P/D/A/>_<MEDIAPOOL>_<RET>_<TIME>
To make diff between Prod,Dev and Acceptance env,
to know target pool and savegroup based retention and start time.
ex : P_LTO5_R1_1800 : Prod, LTO5 Mediapool, Ret1 (for me R1 means <3 months), 
started at 6:00PM

<P/D/A/>_<MEDIAPOOL>_<TIME> or <P/D/A/>_<TIME>_<MEDIAPOOL>
To make diff between Prod,Dev and Acceptance env,
to know target pool and savegroup start time.
ex : P_LTO5_1800 : Prod, LTO5 Mediapool, started at 6:00PM

<P/D/A/>_<SHEDULE>_<TIME>
same except <schedule> is name like applied schedule map :
ex 1F1S1S1 : Full Monday, DIFF Lvl 1 Sun,Tu, Th, Sat, SKIP Wed, Fri
This is best for load balancing

My advice : for more flexibility, avoid matching savegroup name with app name.
you can create all groups you need -eg one starting each 30 min) with a dummy 
"skip all" client
and when needed drop client into the group. All of your config will be ready at 
once,
no need to gather/remember  pool<->savegroup<->retention logic.

For more business oriented view, use app name in group name but not client name,
this to avoid confusion when application is moved from one server to another

In my case ...
All groups have option SAVE_INDEX disabled,
All clients are member of common CFI_and_BOOTSTRAP group, group started daily 
and
manually by savegrp -O at 12:00 by external scheduler.
Backup server and storage node OS are members of
NETWORKER_INFRA group, this one with SAVE_INDEX enabled, and started
by legato, this to avoid bootstrap to be saved with any finishing savegroup.

HTH

Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE
Backup/Storage & System Management

LE FOREM
Département des Systèmes d'Information
Direction Infrastructure

Boulevard Tirou, 104  Tel:    +32 (0)71/206730
B-6000 CHARLEROI      Mobile: +32 (477)/995319
                      Fax:    +32 (0)71/206199
BELGIUM               Mail : Thierry.faidherbe<at>forem.be

"The future belongs to those who believe in the beauty of their dreams", 
Eleanor Roosevelt



-----Message d'origine-----
De : EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] De 
la part de Vygur
Envoyé : lundi 16 avril 2012 23:09
À : NETWORKER AT LISTSERV.TEMPLE DOT EDU
Objet : [Networker] Best Practice in naming Networker Groups?

Hi everyone,
  Currently we don't really have a standard on how our groups are named.  
previously everything was just slapped together and now we would like to have 
an actual standard and clean things up.  What are your best practices for when 
you name a group?

For example name will have retention, server type or app type etc.  (Say 
2yNMMserver)

+----------------------------------------------------------------------
|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