On 2012-11-16 18:29, George Sinclair (NOAA Federal) wrote:

On 2012-11-16 15:36, Michael Leone wrote:

if you use the "clonetime(25)" along with the clone pool (or number
of copies), this should do the job.

Here is the cloneid of one of those savesets:

mminfo -q "cloneid=1352527219" -r

volume,name,copies,savetime(22),clonetime(22)
  volume        name                           copies     date     time
clone time

000001 H:\Users 3 11/10/2012 1:00:19 AM

11/10/2012 9:42:26 AM

000002 H:\Users 3 11/10/2012 1:00:19 AM

11/10/2012 9:42:26 AM

000003 H:\Users 3 11/10/2012 1:00:19 AM

11/10/2012 9:42:26 AM

000004 H:\Users 3 11/10/2012 1:00:19 AM

11/10/2012 9:42:26 AM

Notice that "clonetime" is the clone *start* time, not the clone *end*
time.

Yep! I've always wanted a db attribute that would give me the clone completion time. I think the daemon.raw file is the only way, however. One other thing you could do would be to launch a backup immediately after the clone (assuming you're scripting this), and have it back up some trivial (empty) file to disk. You could then get the completion time for that (sscomp), and you'd know that the clone would have to have completed just prior. That would give you a very close ball park time. If you're not scripting it then savepnpc post-processing might be able to be used to do this, but I'm unclear if the post commands would run before or after cloning, assuming cloning is enabled for the group?

George

--
George Sinclair
Voice: (301) 713-3284 x210
- The preceding message is personal and does not reflect any official or 
unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -