No worries, just bouncing all the available options around. I agree the engine will access the console for its path to the sector, just saying that if a "hard" path is used (eg d:\tngam\sector) then the 2nd engine will look on its own machine for this location. Sounds obvious I know...
1. The clientws and us are local stores that AMO uses to cache data, use for differences since last agent scan and have somewhere to go should it not be able to access the network sector)
2. installing AMO? now thats a tough one (and a big one too). I've been at it nearly 4 years and still it...
Adrian, check that you can actually connect from the engine machine to the sector using the exact name as registered in the console. I have found that at this "early" stage of version 3.2 there are bugs in the engine, for instance I have experienced "Sector Open() Failed...
Just got a 2nd hand HP surestore 6000 DAT drive and tried to install it in my NT server. NT discovered it OK, drivers installed OK etc but each time I tried to backup to DAT I got "invalid media" and "bad tape" showing in NT backup's window. 'Course there is a good chance...
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.