Networker

Re: [Networker] volretent in 7.4.x

2009-01-28 18:12:27
Subject: Re: [Networker] volretent in 7.4.x
From: Francis Swasey <Frank.Swasey AT UVM DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 28 Jan 2009 18:06:16 -0500
Yaron,

I'm sad to report to you that while I first saw this with 7.4.3, it still remains in 7.4.4 and the support person I am working with at EMC states categorically that he cannot reproduce the issue and therefore is sure it is something wrong with my environment. Just having one other person say they are having the same issue is a relief to me.

Thank you,
 Frank

On 1/28/09 3:19 PM, Yaron Zabary wrote:

I am having a similar problems with clones. Mine comes from the fact that I clone to a pool which has its own retention set to three months. When I clone save sets that have a retention of seven days, I expect that the original copy (and volume) will still have a seven days retention, while the clone copy will have a three months retention. What I get is both savesets (and volumes) get a retention of three months. This was under 7.4.3. I just upgraded to 7.4.4 and I hope that this is fixed in 7.4.4.

Francis Swasey wrote:
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