Networker

[Networker] Networker on tru64 updated

2002-11-14 20:57:35
Subject: [Networker] Networker on tru64 updated
From: Richard Hoare <richard AT DATA4U.CO DOT NZ>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Fri, 15 Nov 2002 14:57:31 +1300
One thing I forgot to mention was;

We had created our own directive which did not exclude the /tmp
directory.
If we change the saveset field to specify /tmp the folder is backed up
though no files are included.

The only way we can back this up is by performing a manual backup.

Thanks for the responses so far.



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Stan Horwitz
Sent: Friday, 15 November 2002 2:07 p.m.
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Networker on tru64

On Fri, 15 Nov 2002, Richard Hoare wrote:

> Can someone answer whether by default Networker with tru64 ignores the
> /tmp folder on a full backup.
>
> Is this folder part of the systems swap file?

Yes, and no. The default behavior depends on how you set up each
particular Tru64 Unix client entry. In the client window within nwadmin,
there's a menu of directives options. For example, there is a directive
item that says "netware with compression" and "netware without
compession"
or something along those lines. There's also a directives option that
says
"unix with compression" and another that says "unix without
compression".
The Unix directive (with or without compression) includes skip
statements
to avoid backing up the /tmp directory and some other items.

Think carefully about using this option though. I got burned by it on
one
Tru64 Unix client a couple of years ago. One of the skip directives
causes
the core dump files not to be backed up. This sounds fine, however, we
had
a user create a directory full of html files. This directory was called
"core". Much to our chagrin (and the user's), none of the user's files
was
recovered after that system's disk crashed. That user was not a happy
customer!

A better opton is to manually code your own server side directives file
OR
create a client side directives file to skip the stuff you have no need
to
back up. Either option provides for a much greater level of
customization,
compared to NetWorker's canned directives files.

You can find out more about this stuff by reading up in the NetWorker
administration guide under the "directives" section.

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=