Actually, I just checked the clonetime(20) values and it appears that in
cases where the cloneids are the same, the clonetimes are also. Even in
the example I noted before, it is the case that the clonetimes were all
the same. Can we infer, therefore, that the when cloneids are identical
then the clonetimes are, but not necessarily vice versa?
Is it true that the combined value ssid:cloneid is always unique?
George
George Sinclair wrote:
>
> I have found at least one situation where 4 savesets all have the same
> cloneid but the following properties:
>
> 1. Their ssids are different
> 2. Their savetime(20) are different
> 3. Their nsavetime are different
> 4. The sscreate(20) values are identical for savesets 1 and 2
> 5. The sscreate(20) values are identical for savesets 2 and 3 but
> different from 1 and 2
>
> In most cases, it does appear that the nsavetime is very close to the
> cloneid, but it also looks like in most cases where the cloneids are
> identical, the sscreate times are also, but not in the example noted
> above. Just curious why NetWorker would make two cloneids identical if
> the savetime, nsavetime and sscreate are different?
>
> George
>
> Darren Dunham wrote:
> >
> > > I noticed that several savesets that were not cloned all have the same
> > > cloneid. I understand that every saveset is a clone of itself, and all
> > > savesets should have unique ssids unless one of them is an "actual"
> > > clone of the other, but why would different savesets, each having a
> > > unqiue ssid, have the same cloneids?
> >
> > Were they all kicked off at the same time? Most of my cloneids appear
> > to be identical to 'nsavetime'.
> >
> > $ mminfo -av -r 'ssid,cloneid,nsavetime'
> > ssid clone id save time
> > 559752705 1075927189 1075927189
> > 599987201 1076085426 1076085426
> > [snip]
> >
> > By using a timestamp of when the clone was created, it should be unique
> > for a given ssid.
> >
> > Although I wonder what would happen if you cloned A to B, then kicked
> > off clones at the same moment for A->C and B->D. Presumably database
> > constraints would keep them from getting the same cloneid.
> >
> > > Seems if two ssids are different then their corresponding cloneids
> > > should be too?
> >
> > I see no reason for that.
> >
> > --
> > Darren Dunham ddunham AT taos DOT
> > com
> > Senior Technical Consultant TAOS http://www.taos.com/
> > Got some Dr Pepper? San Francisco, CA bay area
> > < This line left intentionally blank to confuse you. >
> >
> > --
> > Note: To sign off this list, send a "signoff networker" command via email
> > to listserv AT listmail.temple DOT edu or visit the list's Web site at
> > http://listmail.temple.edu/archives/networker.html where you can
> > also view and post messages to the list. Questions regarding this list
> > should be sent to stan AT temple DOT edu
> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
