Networker

Re: [Networker] Fulls inside a differential only policy.

2007-06-21 11:18:22
Subject: Re: [Networker] Fulls inside a differential only policy.
From: "Langford, Paul" <plangfor AT AB.BLUECROSS DOT CA>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 21 Jun 2007 09:06:32 -0600
I haven't tried this with system state, system db, and ASR, but we use it for a 
lot of other backups.  Create a directive that skips system state, system db, 
and ASR.  Add the directive after the first full backup

Paul L,

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]On
Behalf Of Stuart Whitby
Sent: June 21, 2007 6:10 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Fulls inside a differential only policy.


NetWorkers,
 
I'm wondering if anyone has a solution to this issue:
 
In a tape-free environment (2xCDLs only) I've set up NetWorker to do 
differentials.  To keep down the disk space usage, we have to avoid running 
full backups on a regular basis.  Full (level 0) backups will be taken every 
year and kept for 25, Level 1s every month kept for a year, and level 2-8 on a 
daily basis through the rest of the week to be kept for a month.  This is set 
up with full backups from a yearly group going to a yearly pool, monthlies from 
a monthly group going to a monthly pool, and the rest going to a daily pool, 
with pools specified by group and level.
 
The problem with this is when someone adds a new filesystem.  Since this 
environment is either NDMP or Windows, NDMP is no problem to select the pool by 
"full" from any NDMP group goes to the yearly pool.  The problem is that, even 
with differential backups defined, Windows SYSTEM_STATE, SYSTEM_DB and ASR 
savesets are always performed as full backups.  I don't see that this gives me 
any choice but to specify that full backups from a windows group goes to the 
daily pool, but then I end up with any new clients clogging up a tape from the 
daily pool with their first full backup for the next 13 months or so.
 
The best solution I can come up with is to create a (generally) empty group 
called "NewClients" which should be used purely for a client's first backup, 
with this saved to the yearly pool.  Can anyone come up with anything better?
 
Cheers,
 
Stuart.

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

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

<Prev in Thread] Current Thread [Next in Thread>