That long string is the long form of the ssid which is also the name of the
file on the AFTD where that saveset is written.
You can get that same long string by using, for instance, ssid(70) on the
mminfo report.
Try using -r"ssid,ssid(70)" for some other ssid you know that exists in the
AFTD and search for a file with the long name in the AFTD.
Use -q"ssid=some_ssid"for the query
Not sure about this other one but it should work. Use:
-q"ssid=46606136-00000006-61ab8d92-47ab8d92-04a00000-0a4007c8"
for the query and check the status of the offending saveset with -r (use
volume, ssid, cloneid, ssflags, clflags, etc). It may give you some clues.
I cannot tell why the ssid is not found. It is strange...the error comes from
save, which complains because it couldn't "update" that saveset...but update
what? Is the saveset already removed by some automatic staging but save is not
yet done with it? I doesn't make any sense to me.
jee
is the corresponds to the
On Friday 08 February 2008 13:53, MIchael Leone wrote:
> I'm seeing this error when during a clone job:
>
> 39077:save: error, cannot find ssid
> 46606136-00000006-61ab8d92-47ab8d92-04a00000-0a4007c8 to update
>
> 7164:save: shutdown failed
>
> NetWorker 7.4SP1 on Win2003. Cloning to (or is it from?) an ADV_FILE
> device (disk space allocated from SAN), which is attached to a Win2003
> clustered node. What would cause it to not find the SSID? When I examine
> the save sets for that client, I don't see any missing (meaning: I see 3
> copies of each SSID - 1 on tape, 1 on the R/W disk, 1 on the RO disk).
> Unless NetWorker isn't showing me that SSID, which is possible - when I
> wuery the savesets (via GUI), the SSIDs returned are of the form
> "10178757979", and not the form shown above.
>
> The disk resource is mounted. The job lists the folders by name (i.e.,
> doesn't use ALL; we were told that we'd get better performance if we would
> list all the top level folders individual in the client definition). The
> error only seems to happen on one of the 12 or so folders listed. The log
> on the client is useless; no entries during the time period of the backup
> at all. Log from server is also of limited help ...
>
> 38714 2/8/2008 3:24:45 AM 0 0 2 2660 2656 0 admnbck001 nsrd
> admnbck001.wrk.ads.pha.phila.gov:cloning session done saving to pool
> 'PHACLONE' (897368)
> 38732 2/8/2008 3:24:45 AM 0 0 2 2660 2656 0 admnbck001 nsrd cloning
> session:save sets done reading 212 GB
> 38758 2/8/2008 3:24:46 AM 2 0 0 2660 2656 0 admnbck001 nsrd savegroup
> failure alert: NT_SAN1 Completed/Aborted, Total 1 client(s), 0 Clients
> disabled, 0 Hostname(s) Unresolved, 1 Failed, 0 Succeeded.
> 38758 2/8/2008 3:24:46 AM 2 0 0 2660 2656 0 admnbck001 nsrd savegroup
> alert: NT_SAN1 completed, Total 1 client(s), 1 Failed. Please see group
> completion details for more information.
> Unable to render the following message: * nt_san1:H:\departments
> 39077:save: error, cannot find ssid
> 46606136-00000006-61ab8d92-47ab8d92-04a00000-0a4007c8 to update
>
> Unable to render the following message: * nt_san1:H:\departments
>
> Unable to render the following message: * nt_san1:H:\departments
> 7164:save: shutdown failed
>
> Unable to render the following message: * nt_san1:H:\Users Cannot
> determine status of backup process. Use mminfo to determine job status.
>
> 12662 2/8/2008 3:24:46 AM 2 0 0 2660 2656 0 admnbck001 nsrd runq: NSR
> group NT_SAN1 exited with return code 1.
> 42506 2/8/2008 3:24:49 AM 2 0 0 2660 2656 0 admnbck001 nsrd write
> completion notice: Writing to volume 897368 complete
>
>
> Any and all help appreciated.
>
>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|