Re: [Networker] Cloning
2006-02-17 09:07:14
Thank you all very much for the fast responses.
Tim
Rock, Jerry wrote:
>Every saveset has a "ssid" and "cloneid". Therefore, after you've
>cloned, you'll have 2 savesets in your index. Example:
>
>First saveset would be something like this (ssid/cloneid):
>
>256784594/12345678
>
>Second saveset would look like this:
>
>256784594/98756754
>
>You'll note they have the same ssid, but different cloneid's.
>
>If you do the following, you can delete a saveset, while keeping a
>clone:
>
>nsrmm -d -y -S ssid/cloneid -> nsrmm -d -y -S 256784594/12345678
>
>Clone -> 256784594/98756754 would still be in the index.
>
>After that, you'll have to do some index management to clean up:
>
>nsrim -V volume_name
>
>Jerry Rock
>Sr. Systems Engineer
>Structured Technologies, Inc.
>
>-----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
|
|
|