|
Re: [Networker] About .nsr local directive..
2006-12-08 10:20:33
Perhaps a cron job that runs on all the clients and reports .nsr files,
say once a month, might not be
a bad idea. This way, their existence and justification can be re-evaluated.
One of the primary reasons for doing it on the client is that longer
directives on the server side used
to cause problems. I thought there was a limit but never knew what it
was. Maybe this was fixed
in later releases?
Also, if you just want to skip some data one night, it's much easier to
just create the client side directive
because that's a quickie. Having to do it one the server means having to
create the directive, save it and
then go and edit the NSR client resource ... to much work.
George
Maarten Boot wrote:
It would be nice if networker had a diagnostic switch to tell us during backup:
* warning: ".nsr file present at path:<path>
contents:
Maarten
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Curtis Preston
Sent: Friday, December 08, 2006 8:18 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] About .nsr local directive..
That's really interesting, Darren. I never thought about this "problem"
created by changing directives. Always nice to learn something.
For what it's worth, I hate .nsr files. I can't edit them from the backup server, and I think they create surprises for later generations of backup admins, and you can accomplish the same thing by using server-side directives.
I was recently bitten by user-level bp.conf files in a customer's environment.
(That's a NetBackup thing, but the concept is the same.)
---
W. Curtis Preston, Author of Backup & Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Darren Dunham
Sent: Thursday, December 07, 2006 8:09 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] About .nsr local directive..
Today¡¦ I move that filename to .nsr_old for backup all *.dbf files.
But.. All of *.bdf files are not backed up.
It means .nsr_old directive file are working all the same..
Were the files changed between the backups? The new 'save' process
won't know that the files are missing from the backup due to directives.
It'll just look at the timestamp.
If you change directives to make things less restrictive, you probably
want to run a full backup.
--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- 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
|
|
|
