Hi Tim
>How can they remove the oldest cycle without loosing the clone saveset too?
NetWorker users have worked around this in various ways for years. But
NetWorker V7.3 (finally) provides the ability to have different retention
policies for clone savesets. So, your customer could set the retention
policy for the backup savesets to 2 months, but set the retention policy for
the clone savesets to a longer period. Here's a quote for the NetWorker
V7.3 Administrator's Guide (from p. 239):
"Clone data is given the same browse policy as the original save set.
However,
the retention policy for clone data can be specified independently. In this
way,
clone data can be recovered after the retention policy of the original save
set
has expired."
Also, there are two methods of storing disk-to-disk backups with NetWorker:
- file type device (FTD)
- advanced file type device (AFTD)
See the section "NetWorker DiskBackup" on p. 260 of the NetWorker V7.3
Administrator's Guide, especially Table 35 on p. 275, which does a great job
of summarizing the differences between the two disk-to-disk backup options.
I believe that you can remove savesets from an AFTD, and have the removal
really free up the disk space.
Finally, the situation you describe (backups to disk, followed by cloning to
tape and deletion from disk) is exactly what the NetWorker 'staging' feature
was created for (since you didn't mention using it, I thought I'd point it
out). You can set knobs in the staging policy to control what events cause
staging to occur. From p. 256:
"Staging can be driven by the following:
* Calendar-based process, such as keeping the save set for 30 days on the
staging device before moving the data to the next device.
* Event-based process, such as when available space in the staging pool
drops below a set threshold. When this happens, the oldest save sets are
moved until available space reaches a preset upper threshold.
* Administrator-based process, such as allowing the administrator to either
reset the threshold or manually select save sets to stage.
Staging does not affect the retention policy of backup data. Therefore,
staged
data is still available for recovery.
Note: If a file type device is on a storage node that is running NetWorker"
See Chapter 10 for details.
Hope this helps!
tl
Terry Lemons
CLARiiON Appliance Engineering
CLARiiON Application Solutions Integration
EMC²
where information lives
4400 Computer Drive, MS D239
Westboro MA 01580
Phone: 508 898 7312
Email: Lemons_Terry AT emc DOT com
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
Behalf Of Tim Verbois
Sent: Friday, February 17, 2006 5:36 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Cloning
Hello,
one of our clients is working with a backup server with local disk
storage. They do a backup to disk devices (instead of tape drives) and
have a L9 robot attached to the server too. Once a month they perform a
full backup and clone this to the tape drive. After 2 months, the data
has to be removed from the local disk drives, but this is not so easy.
1 disk device is 400 GB, and a full backup is 100 GB. They need 4 fulls
to fill a disk drive (but that's 4 months). How can they remove the
oldest cycle without loosing the clone saveset too? You can relabel the
volume, but then you have to wait until the last saveset is 2 months old
(and the oldes 6 months).
--
Tim Verbois
EDS-Telindus
Unix Team
02/553.71.73
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
wit 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
wit 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
|
