Verify Clone Status

[sryth]

Can someone please explain the clflags field to me? I thought that an i meant that the clone was incomplete, yet I have several clones that are complete, but have the i flag set.

Also, I thought the 'a' flag indicated that a clone was aborted, yet I have personally aborted the cloning of a saveset, but the flag was not set.

Am I wrong about these flags? Is there any way to verify the real status of a saveset? While I'm asking, is there any way to easily verify that all savesets in a series have at least 1 successful clone?

Any help is appreciated!

Damien Gregory

 

[TDun]

a=aborted, i=incomplete, s=suspect(read error).

If you want to check if there are clones, do an mminfo with a q "copies>1"
Identify the volumes used, then do an mminfo on the clone volume and check the ssflags for a Finished flag.

 

[sryth]

That's what I thought, but I can see that they are not accurate. I have clones that are complete with the 'i' flag still set. I have clones that have been aborted with no 'a' flag set. Is there another way to verify the clone?

Damien Gregory

 

[TDun]

It is still a saveset, as I said earlier, check the ssflags for teh saveset on the clone volume.

 

[sryth]

It doesn't seem that the ssflags field represents the status of the clone. It seems to be identical to the status of the original saveset. Isn't that why they made the clflags field? Either way, here's some output:

$ mminfo -q ssid=2232430081 -r volume,clflags,ssflags,client,name
volume clflg ssflags client name
000075 CvF 01msgpr001 <8>MSEXCH:IS
900367 aEi CvF 01msgpr001 <8>MSEXCH:IS
900368 CvF 01msgpr001 <8>MSEXCH:IS

The clone on volume 900367 was manually aborted, the ssflags are all identical.

$ mminfo -q ssid=2237184001 -r volume,clflags,ssflags,client,name
volume clflg ssflags client name
000099 vF 01msgpr003 MSEXCH:IS
900367 i vF 01msgpr003 MSEXCH:IS

I watched this clone finish, yet the 'i' flag in clflags is still set.

Unfortunately, I've relabeled the tape that had the saveset that was aborted, but had no 'a' flag set in clflags.

Is this a common problem? Is there a fix/workaround? My search continues :-(

Damien Gregory