Eberhart, Deborah wrote:

Thank.  But... If there is a clone id doesn't that mean a clone was made?
If so then how can some of the clone id's say there is only 1 copy.  (If 1
copy means it is just a copy of the data off the drive.)

Deborah Eberhart
BB&T Legato Team
(252) 246-2719
deberhart AT BBandT DOT com

No, a clone id does not mean a clone was made.  Every saveset has a
clone id in the media database, even the original.  The combination of
saveset id and clone id is always unique so you can pick which copy of a
backup you want to work with using this combination.  1 copy means just
that there is 1 copy of this data known to Networker (the original
backup) 2 copies means Networker knows about 2 copies the original plus
one clone.  By Networker I mean more specifically the media database.
If you have savesets for which you believe a clone was made and mminfo
is only reporting one copy, then the media database and therefore the
rest of Networker, does not know about this clone copy.  So, it either
was not copied successfully or somehow the media database has lost track
of it.  This can happen if a volume is relabled or deleted from the
media database.

-----Original Message-----
From: Stan Sander [mailto:ssande AT sandia DOT gov]
Sent: Friday, June 06, 2003 9:39 AM
To: Legato NetWorker discussion; Eberhart, Deborah
Subject: Re: [Networker] mminfo questions


Eberhart, Deborah wrote:

Hi,

I need to get clarification of some options for mminfo.  The options are
copies, cloneid.  For the option copies, I believe that a response of 1
means no clone was created.  It is just a backup "copy" of the data from

the

drive.  The response of 2 means there is the original backup and a clone
"copy" of the data.  I am guessing that the response of 3 would mean there
is the original backup and two clones of  the data.  We are not setup to
have two clones per saveset so why would it even try to create two clones
instead of just one.  For the option of clone id, how can multiple

different

savesets have the same clone id?

<snip>

You are correct in your assesment of the clone id and it's meaning.  As
for why it would try to create more than 1 clone, my experience has show
that this is an "undocumented feature" in Legato.  I call it an
undocumented feature since we all know that Legato doesn't contain any
bugs.   ;-)  As for why multiple different savesets would have the same
clone id it is because they were completed at the same time.  The clone
ID bears a striking resemblance to epoch seconds.  Unix folk will know
what I mean by that but for the rest of the world it is the number of
seconds elapsed since January 1, 1970 UTC time.

--
Stan Sander - CSU Special Projects
Unix Systems/Server Administrator
(505)284-4915

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=