You dont need /nsr/tmp it has all temporary data that is needed by current
instance of savegroups & daemons, but all that is tmp, as Frank said
deleting will not create any problem unless you are removing it when daemons
are running.
Just to add, u need sec directory under tmp in case you do not want to loose
the current group details, by that what I mean is, if you delete sec you
will not be able to restart(resume) the savegroups, after restarting the
daemons all groups will be marked as completed (green checkbox status). sec
contains saveset level info i.e which savesets completed,which failed and
which never ran. If you restart a failed savegoup incomplete & failed
savesets will run again.
You can always start the group which will start all clients in that group
and all savesets again.
Keeping sec might be useful in some cases mainly if u have a huge data zone
and multiple failures in same savegroup which u might need to resume after
restarting services.
In few cases I saved a lot of time & manual work by keeping sec.
Regards,
-Punit
On Fri, Jul 23, 2010 at 10:06 PM, Francis Swasey <Frank.Swasey AT uvm DOT
edu>wrote:
> On 7/23/10 12:27 PM, George Sinclair wrote:
> > A few questions here on /nsr/tmp.
> >
> > It's currently only 4.6 MB, and it's not being backed up as there is a
> default /nsr/tmp/.nsr
> > file to skip everything under there, so I'm assuming that EMC doesn't
> consider this information
> > vital.
> >
> > 1. *If* you shut down NW first, is it safe to remove everything under
> /nsr/tmp ?
>
> Yes.
>
> >
> > 2. When you re-start NW, will it automatically re-create the 'tmp'
> directory, or will it be
> > necessary to first manually re-create it before restarting NW?
>
> NW will recreate the /nsr/tmp directory when it is started up.
>
> >
> > 3. I see a number of older lock files under /nsr/tmp and lots of client
> completion information
> > files named like:
> >
> > /nsr/tmp/sg/groupname/ss.client.blah-blah-blah.
> >
> > It looks like these get replaced each day, but regardless, do I really
> need any of the stuff
> > under /nsr/tmp?
>
> No -- as long as you don't remove it while NW is running.
>
> >
> > Will removing everything under tmp cause any headaches to NW, e.g. give
> it heart failure or
> > cause it to fail to operate properly, wherein maybe somehow it might
> expect to see previous
> > information stored under there somewhere, but now it can no longer access
> it?
> >
> > 4. Is it recommended to periodically clean out tmp?
>
> I remove it every time I cycle NetWorker just to keep the cobwebs from
> getting too thick.
>
> >
> > Thanks.
> >
> > George
> >
>
> --
> Frank Swasey | http://www.uvm.edu/~fcs
> Sr Systems Administrator | Always remember: You are UNIQUE,
> University of Vermont | just like everyone else.
> "I am not young enough to know everything." - Oscar Wilde (1854-1900)
>
> 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
>
--
Regards,
Punitsingh Suryawanshi
Service Delivery Consultant
Hewlett-Packard, Bangalore, India.
+91 966-337-5500
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
|
