Allan is right. Differentials should do something pretty close to what you
need. A differential backs up data that changed since the last
lower-numbered backup. A full is level zero. So create a schedule called
"Level 9" with a full on the day of the week you want and level 9 on the
other days. Then create another called "Level 5" with a full and level 5.
In the client definition that runs in group 1, select schedule: Level 9. In
the client for group 2, select schedule: Level 5. As long as group 1 always
runs before group 2, both will back up changes since the last full.
Conrad Macina
Pfizer, Inc.
On Tue, 19 Jul 2005 10:13:20 +0100, Allan Nelson <an AT CEH.AC DOT UK> wrote:
>Might it be feasible to use differential backups rather than incremental?
>
>Allan.
>
>
>-----Original Message-----
>From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT
>EDU] On
>Behalf Of Nick Tan
>Sent: Tuesday, July 19, 2005 5:58 AM
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: [Networker] single client in multiple groups
>
>Hi All,
>
>I have a client which is in two groups. This is what is happening:
>
>Group 1 runs first and does a full backup. The size is 5GB
>Group 2 runs later that night and does a full backup. The size is 5GB.
>
>Looks good so far. During the day, the clients creates 3GB data.
>
>Group 1 runs first and does an incremental. The size is 3GB.
>Group 2 runs later that night and does an incremental. The size is
>500kb.
>
>It looks like both groups are sharing the same file index. Is there a
>way to make it so each group reads its own index. In the example
>above, I want Group 2 to be backing up the 3 GB in the incremental as
>well as group 1.
>
>I am running Networker 7.1 on Solaris 8. The client in question is
>Solaris 8 also.
>
>Thanks,
>
>Nick
>
>--
>Nick Tan
>Unix Systems Manager
>The Walter and Eliza Hall Institute
>nick AT wehi.edu DOT au
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listserv.temple DOT edu or visit the list's Web site at
>http://listserv.temple.edu/archives/networker.html where you can
>also view and post messages to the list. Questions regarding this list
>should be sent to stan AT temple DOT edu
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listserv.temple DOT edu or visit the list's Web site at
>http://listserv.temple.edu/archives/networker.html where you can
>also view and post messages to the list. Questions regarding this list
>should be sent to stan AT temple DOT edu
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listserv.temple DOT edu or visit the list's Web site at
>http://listserv.temple.edu/archives/networker.html where you can
>also view and post messages to the list. Questions regarding this list
>should be sent to stan AT temple DOT edu
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|