Did the error msg cause your recovery to fail? Or did you just see the msgs during the restore? We see that all the time on our metaframe clients and SQL clients. What type of server/data are you recovering? We get that msg during SQL recoveries because we aren't running the SQL-aware module for legato, but the recovery completes
Msg causes recovery to fail.Approximately 10 minutes later since I begin recover, file size changes from 0 to 64K.Thats all.
File is a SQLServer dump file.
I tried a directed recover from a client and hit a bug. According to documents Legato 6.0.1 sometimes loses its index structure.I rebuilt index for a tape by using command "scanner".
Next recover trial succeded.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.