Networker

Re: [Networker] Index / Boostrap saving issue

2009-05-27 09:49:47
Subject: Re: [Networker] Index / Boostrap saving issue
From: "Coty, Edward" <Edward.Coty AT AIG DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 27 May 2009 09:44:39 -0400
See below.



EDWARD COTY

LEAD STORAGE ENGINEER, LCNA, NACP

WORK - 973-533-2098

CELL - 973-296-0918

EDWARD.COTY AT AIG DOT COM





-----Original Message-----
From: James Pratt [mailto:jpratt AT norwich DOT edu]
Sent: Wednesday, May 27, 2009 9:38 AM
To: EMC NetWorker discussion; Coty, Edward
Subject: RE: [Networker] Index / Boostrap saving issue



Thanks for the advice - I've seen it mentioned a few places that one should 
"place the server and all clients in a group" to backup all client indexes and 
bootstrap - doesn't' this mean I will need separate client resource instances 
for every NW client, copied from originals so the clientid is the same? No one 
client entry for each client server. The client should belong to two different 
groups. The regular schedule group which should have NO INDEX SAVE checked off. 
The other group is disabled and is run with the savegrp -O command.



Do you set this group to disabled and just run the bootstrap/savegrp -O daily 
manually? Yes or create a job and schedule it daily. I guess I don't understand 
why just doing a daily NW server backup or NMCASA  db backup for 
bootstrap/indexes is not enough -Doing an NMC DB backup does not protect you 
from a Networker DB corruption. You can just let all indexes run when the 
client backup is complete and a bootstrap backup after every group completes 
but this overhead will hurt you backup performance. But doing all the meta da 
it also seems a bit weird to have to put all the clients in one group, 
especially if they are very different such as NDMP/exch module, file level, VCB 
, etc ..Putting them all in one group is so you can backup the client indexes 
and server bootstrap. This is totally different then Exchange backups or file 
level backups.



(Then again, I never had formal training on NW, so perhaps I'm missing 
something painfully obvious - if so, my apologies!)



Thanks!

Jamie



-----Original Message-----

From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Coty, Edward

Sent: Wednesday, May 27, 2009 8:14 AM

To: NETWORKER AT LISTSERV.TEMPLE DOT EDU

Subject: Re: [Networker] Index / Boostrap saving issue



Yes. You can please your backup server into its own scheduled group. Assign it 
a schedule that skips backups everyday.



Also place the server and all clients into another group. Run this everyday, or 
whatever days you want to by running savegrp -O groupname. This will backup all 
client indexes and bootstrap.



I would suggest trying to backup the indexes and bootstrap at least once a day.



EDWARD COTY

LEAD STORAGE ENGINEER, LCNA, NACP

WORK - 973-533-2098

CELL - 973-296-0918

EDWARD.COTY AT AIG DOT COM



-----Original Message-----

From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of kurianv

Sent: Wednesday, May 27, 2009 12:34 AM

To: NETWORKER AT LISTSERV.TEMPLE DOT EDU

Subject: [Networker] Index / Boostrap saving issue



i think i shud take back what i have said because bootstrap and index runs 
which ever group backup server is added...and i have included both the daily 
group and weekly group for index pool.



But still is there anyway to make bootstrap run on specific day and not every 
days.



Regards,

kv



+----------------------------------------------------------------------

|This was sent by kurianji 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

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