Michael,
You are reading it wrong.
I am expecting the volretent for the original tape in the Default pool
to match the clretent value. That ssid is the only saveset on the
volume. So, for a test that I ran today, I expect the volretent to be
04/28/09 on the default volume, and 01/28/16 on the default clone volume.
What I am getting is that the volretent of both the default and default
clone volumes (both of which have just the one saveset on them) is
displaying as 01/28/16 after running nsrim -X.
# mminfo -q ssid=2206232840 -r volume,savetime,volretent,ssretent,clretent
volume date expires retent clretent
Default.001 01/28/09 04/28/09 01/28/16 04/28/09
Default.Clone.001 01/28/09 01/28/16 01/28/16 01/28/16
# nsrim -X
<snip>
# mminfo -q ssid=2206232840 -r volume,savetime,volretent,ssretent,clretent
volume date expires retent clretent
Default.001 01/28/09 01/28/16 01/28/16 04/28/09
Default.Clone.001 01/28/09 01/28/16 01/28/16 01/28/16
Frank
On 1/28/09 1:09 PM, Michael Nored wrote:
Frank,
I may be reading your question #7 wrong but if the only save set (/etc) on
the tape has a 3 month retention what are you expecting the volretent to be?
I believe that the volretent period is based on the longest retention period
of any save sets written to the tape.
volretent time 9 The date the last save set on this
volume will expire.
If only want to keep the save set for 3 months but want the cloned save set
for 7 years why would you want to have a 7 year volretent on the Default
tape?
Michael Nored
Consultant
Nored Consulting, LLC
M: (407) 399-8162
T: (352) 350-7142
E: mnored AT Netzero DOT net
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Francis Swasey
Sent: Wednesday, January 28, 2009 12:13 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] volretent in 7.4.x
Folks,
I have been working a problem with EMC since Thanksgiving. And it's
not going so well. They are hinting that I've got mediadb corruption --
but they aren't saying that...
What I am doing is using the -y flag on nsrclone to give my clones a
longer retention time than the original ssid that I'm cloning. mminfo
tells me the correct clretent value for the copy on the original volume,
but tells me the volretent for the original volume (seemingly) based off
the ssretent value which has the longer time for the copy I cloned and
sent to the vault.
EMC tells me they can't reproduce the problem. I can very reliably
and I thought I remembered someone else that was talking about volretent
values being wrong in 7.4 on this list -- of course, I can't find that
post with the searches I've been doing this morning.
Here's how I am able to reproduce it.
1) label a tape into the "Default" pool (which I do not use)
2) pick a client and run "save -y '3 months' -b 'Default' /etc" on it to
create an ssid
3) mminfo -q volume=<volume just used> -r ssid,cloneid
- get the ssid and clone id
4) nsrclone -b 'Default Clone' -y '7 years' -S <ssid>/<cloneid>
5) mminfo -q ssid=<ssid> -r volume,pool,volretent,ssretent,clretent
- both volumes will be correct at this point with volretent == clretent
6) nsrim -X
7) mminfo -q ssid=<ssid> -r volume,pool,volretent,ssretent,clretent
- The volume in the Default pool, will now have volretent == ssretent.
Can anyone verify that I'm not blind deaf and dumb.
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
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
|
