No, that is not the only way. You can avoid scanning altogether.
Just simply make your local tape drives a storage node off of your remote server. The data will be written to your local tape drives and the index information will be written to your remote server. Once the backup is finished...
I ran into this problem the other day. Its a permissions problem in Windows. Legato service does not have the required permissions to walk the file system.
We got around this problem by starting the Legato service as the "local administrator".
The NT admins are still trying to figure out...
I used the Emulex procedure so I could see the drives via hbanyware. I will wire the drives next week and discover them. I still have some time before the lease on the existing backup server expires so I can rebuild the new one with 9 if necessary.
I would only use a SN if you need maximum performance ... for example we have a server that has SAN disk, has 2 fiber cards dedicated to this, and 2 fiber cards for tape .. 2 drives to each fiber card ... we get about 80Mbs with this set up. We only achieved this thruput when this server was...
A lot depends on what you want to accomplish. If you want maxmimum throughput you would have a tape drive or 2 directly connected to one of the SAN servers, preferably with its own fiber card (use a different fiber card for your disks), and set it up as a storage node ... but you will have to...
Had the same problem with NW 7.2 on Unix. I had to apply a "jumbo" patch to the UNIX NW 7.2 server and that fixed every thing. Legato changed the way it handled Netware backups in 7.2 because Netware still backups up in 2 GB chunks and this caused problems with restores from the Netware...
We had a similar issue after moving to 7.2. The Novell servers would get "can't retreive volume information" every time they tried to "view required volumes". Legato sent new files ansrd ... nsrd ... etc. That too care of the problem.
On the target system you will have to change the setting in the UTL config file to point to the source client:
client="source target client name"
In the source client configuration you will have to give the target client permission to look at the source targets backup (remote access).
If your...
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.