Hi Nelson,
you can think of the cloneid as a "nclonetime".
Note: If you run "nsrinfo -t cloneid clientname" you don't get information
from any backups (unless there is a big coincidence here).
I suggested using nsrinfo with the cloneid just to see if the date produced
by nsrinfo would match the clonetime
So, if you run the original mminfo command but adding the cloneid:
mminfo -v -q "copies>=3,clonetime>=7-Sep-2011,
pool=ddclone" -oct -r"client,name,totalsize,clonetime(16),ssid,cloneid"
what would be the date produced by nsrinfo using those cloneid's for each
clone that shows a clonetime in the future? Would the cloneid's date match
the clonetime?
jee
On Friday 09 September 2011 09:17:12 Nelson, Allan wrote:
> Hmmm - I'll investigate this further.
> I just listed the ssid/cloneid's for the clones done yesterday and (maybe
> this is correct I don't know, I need to look into it) but I see this sort
> of thing (taking just 2 different clients as an example)...
>
> Client name ssid cloneid clonetime
> Client1 filesys1 3747738242 1315447564 09/08/2011 03:06
> Client1 filesys2 3865399286 1315447564 09/08/2011 03:06
> Client1 filesys3 4167164356 1315447564 09/08/2011 03:06
> Client2 filesys1 4200943471 1315447564 09/08/2011 03:06
> Client2 filesys2 4348749181 1315448644 09/08/2011 03:24
>
> I thought the cloneid would be unique? But perhaps it's just the
> ssid/cloneid combination that's unique? The cloneid's match up with the
> clonetimes obviously.
>
> Jee - I tried the nsrinfo command you suggested. Hope I got this right,
> but taking one of the cloneid's above, I see this...
>
> nsrinfo -t 1315447564 Client1
> scanning client `Client1' for savetime 1315447564(Thu 08 Sep 2011 03:06:04
> AM BST) from the backup namespace 0 objects found
>
> I've tried several others and get the same response.
>
> I also tried...
> nsrinfo -n all -t 1315447564 Client1
>
> But got the same result.
>
> I did recover files from a clone last month so I'll try another and check I
> can!
>
> Cheeers... Allan
>
>
> -----Original Message-----
> From: jee [mailto:jee AT eresmas DOT net]
> Sent: 08 September 2011 20:54
> To: EMC NetWorker discussion; Nelson, Allan
> Subject: Re: [Networker] Clone time...
>
> souns like a bug...
> what time is printed by nsrinfo when you use the cloneid as the nsavetime?
>
> (e.g "nsrinfo -t <CLONEID> <CLIENTNAME>" )
>
> jee
>
> On Wednesday 07 September 2011 14:01:28 Nelson, Allan wrote:
> > Hi
> > I'm just doing some cloning and used an mminfo command to see how things
> > were going...
> >
> > mminfo -v -q "copies>=3, clonetime>=7-Sep-2011, pool=ddclone" -oct -r
> > "client, name, totalsize, clonetime(16)"
> >
> > I'm a bit confused about the clonetime I'm seeing for a couple of
> > reasons...
> >
> > 1) For some I'm seeing a time in the future - for example, I looked at
> > 13:30 and I saw several savesets listed with a clonetime of 13:36
> > (checked time on server and PC I'm using and they're fine). 2) I see
> > there are 'blocks' of savesets all with the same clonetime. I thought
> > clone operations were sequential, so how come they show the same time.
> >
> > I'm not particularly worried about it, just trying to understand why I'm
> > seeing what I'm seeing.
> >
> > Cheeers... Allan.
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
|
