Unsolved

This post is more than 5 years old

10 Posts

923

October 21st, 2007 23:00

Save Set Cloning Failed: How to retrieve the SSID in 7.4?

Hello,

In my report, I got the message "Automatic cloning of save sets to pool LTO3Clone failed." In the older versions of Networker, we were able to retrieve the SSID of the failed cloned in the daemon.log at the end time of the group. I don't retrieve this kind of information in the daemon.raw. Where do we find this information now?

Thank you for your help,
William

32 Posts

October 22nd, 2007 02:00

find a solution here for you. don't know if it'd help

http://solutions.emc.com/emcsolutionview.asp?id=esg50728

Use mminfo command as follows:


If know the volume name of the tape that failed, you can do something like

mminfo -q volume="TheFailedVolume:001" -r 'ssid,client,name,savetime'


Once comfortable with info for the right clone volume, remove everything but the

'ssid' from the '-r' (report) specification. this will give a list of saveset IDs that would need to be cloned again; which you can combine with nsrclone into one commandline (UNIX only): i.e.

nsrclone -b "TheClonePool" -S `mminfo -q volume="TheFailedVolume:001 -r ssid"`

10 Posts

October 22nd, 2007 02:00

How should this help me? It gives me the complete list of all the ssid. I only need the failed clones from the full backups of the last week-end.

32 Posts

October 22nd, 2007 02:00

mminfo -av -r "volume, ssid, ssid(55), cloneid"

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

October 22nd, 2007 07:00

You can check number of copies and clflags as well to checj validity of cloned ssid (as broken copy will increment count as well).

10 Posts

October 22nd, 2007 07:00

Thank's to try to help me but no, it doesn't help because the group contains 92 servers and the report doesn't tell me which server has failed its clone, so I don't know on which tape it is...

10 Posts

October 24th, 2007 04:00

And how do I do that?

This mean that the info disappeared from the daemon log?

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

October 24th, 2007 05:00

With mminfo. As for daemon.log, I didn't check how this works now in 7.4, but with mminfo you can't go wrong much. I would suggest to open that with support - they will probably get official response by EMC for that and perhaps open RGE/bug incident (depending on what EMC will have to say about that).
No Events found!

Top