Unrecognizable Virtual Volumes on SSID 1

[ChickBladder]

We are working w/ Legato Networker 6.1 connected to a SAN w/ the Store-Age Virtual engine. The backup server is Solaris 2.6. We have assigned 10 Virtual Disks from the SAN directly to the backup server (not my suggestion). Half of the "Vdisks" Virtual disks seem to drop out of the SSID index. Any help would be most appreciated!!!!
Below is an example of what the output of a proper SSID

*
April 04 17:18 2003 dbgs3000 bootstrap information page1

date time level ssid file
record volume
02/28/03 22:30:00 full 1614284289 222
0 DBGS-Full-0368
*

 

[605]

I do not understand your message - what exactly do you mean by "dropping out" ? - I guess you mean that the SSID looks
to "large" (1614284289) but this is just my guess.

If so, what is the problem ? - the ssid is a complex value,
compared to the old one (NW 5.x) it does not increment with
each new save set any more.

The only important question is: Can NetWorker recover this
save set (can he resolve the SSID to the physical location).

 

[bbstacker]

re: Chickbladder's thread;
We have been using Legato to back
up our Virtual Volumes and have notice by looking at the Indexes tool on Networker that the Save Set Id's have been wiped out. When you click on the Instances button in the Index tool that is empty also. Furthermore, a back-up was done on these volumes and tape# logged. Also, when you check the Volume tool on Networker and perform a scan using the tape number (you thought held the backed-up volume) there are no Save Set Id's associated with the tape#. The size of the Volumes range between 400 and 800 gb. So, if you want to restore lost data you cannot, because you have no Save Set Id's to use as a reference point. This only appears to be happening on Virtual Volumes.

??????

 

[605]

This looks very strange. As you know, NetWorker assigns a
volume id to the volume and a save set id for each save
set. He stores it in the media database AND on tape. That's
why you can scan in the media and repopulate the indexes
with "scanner".

You must not even tell NetWorker the "tape number" (i think
you are talking about the volume name or the volume id).
This is mandatory, as NetWorker can in fact scan-in any
other NetWorker tape as long as it has been written with a
compatible device AND the same block size.

This is how you can add a media from any other NetWorker
data zone (via data exchange). As long as NetWorker has
not scanned the media, he does not even know the ids.

While doing this, you MUST see these references on the
monitor. If not, there is a reading problem. But scanning
so far has nothing to do with data recovery at all. This is
another step that of course needs a volume id and ssid, as
stated correctly.

Now, besides these facts, that you obviously have recover
problems, i cannot see why this should happen only on
virtual volumes that have been backed up.

To me the scanerio looks more like a corrupt media database.
However, this still would not explain why you would not see
any info during the scan process.