On 13/10/2009, at 10:34 , Werth, Dave wrote:

> It seems to me the problem with this type of copying is that you end 
> up losing the information about which system the backup was originally 
> made from and perhaps the directory structure, ownership, etc.

Yes and no : You could perform all recovers and apply diffs from NB and 
backup the new fulls to Networker but using a logical path :

ex : 
/NB2LGTO/DATA/<original_client>/date/level/<original_path>
/NB2LGTO/DATA/<original_client>/<original_path>/date/level

Doing so, you can retrieve when data has been originally 
backuped (the date in the networker path name), original backup
level and keep original file structure (original server, drive path).

Dedicating all NB restore on 1 networker client will make
restore life easier in networker env, all NB recovers done on
1 unique client name. This will not mix actual prod data's retention
with old one. Storing NB backup level in logical path will
allow you to keep versionning.

To avoid exploding index size, consider archiving
the recovered data in networker in way of backuping.
Preserve index space by generating a recursive ls -l or dir /s
you store in a text based file in the root of the archived path.
It will be archived at same the logical path. Keep it also in 
another location for easier lookup.
eg under /NB2LGTO/IDX/<original client>/, file called SSID.log
where SSID is the Legato's reference of "migrated" data.

In anyway, system state cannot be recovered. Take care for old
data saved by modules : You may need original application version
to retrieve the data. 

As most of the old windows backups will not be recoverable 
due to hardware change, different HBA drivers, .... 
focus only on data you really need to migrate from NB to Legato
and drop the unnecessary set of tapes.

HTH

Th

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