Hello, Simon,

One other way to handle this, other than the cron job method, is to use
a server side directive. Create two instances of the client. Client
instance 1 lists 'All' for the savesets, or minimally /home, but uses a
custom directive with the value:

+null: /home/username/archive

It would be in group A with schedule A. Schedule A can be whatever you
want.

Client instance 2 uses 'Unix standard directives' but lists the
following saveset:

home/username/archive

It would be in group B with schedule B. Just make schedule B run a full
on weekends and 'S' or skip on all other days.

You could use +skip, but the problem with skip is that depending on
which group runs first or which one ran last, t he index entries would
get marked out and your browse capability might not show the files. In
other words, when the second group runs it would update the index, but
when the first group runs, it would wipe out (cover over) what the other
one had done in terms of what shows up in the browse window for the
affected path. Could override this by fully specifying the path. I've
had luck with that before, but no matter how you arrange the start
times, will be a nuisance. +null accomplishes same thing but does not
remove index entries, just doesn't back anything up, but again, even
though it says to skip the data, it will not remove the index entries
like skip does.

So, cron job or server side directives? AS the saying goes, choose your
poison.

George

Simon Delicata wrote:
>
> Hi all,
>
> I've been puzzling over this problem for a few days and haven't thought of
> a way around it. I would like to restrict a particular subfolder of
> (archives) from being backed up during an incremental, and only let them
> get backed up on a full, i.e
>
> /home/username/   gets backed via an incremental every night
> /home/username/archive  only gets backed up during a full over the weekend
>
> Is this at all possible ?
>
> Kind Regards and TIA
>
> Simon Delicata
>
> Networker 6.1.4 running on Tru64
> Client 7.0 running on Redhat 8.0
>
> --
> Note: To sign off this list, send a "signoff networker" 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 networker" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=