I've had similar dynamic registration problems on a reboot, when the a domain controller was also a DNS server that was AD integrated. Basically, if the domain controller was pointing to itself (in the LAN connection settings) as its primary DNS server, when it was rebooted an attempt to...
A scratch set is the set of tapes within a media pool where retention period specified for the pool has expired. The Save set is the set of tapes were the retention period has not expired. Probably the retention period for the tapes has not expired so they are still in the save set for the media...
Hmmm... that is weird... Although you should not be getting access denied errors... The account that is being used to do the COPY job should have full access to the files and folders on the source. You should probably check to make sure that is the case. I suspect the account does not have...
The copy job has several different options - Delete Files, Mirror, Create Empty directories, and Copy File Security Info.
Delete option cause the source files to be deleted after they are backed up to tape... this is sort of like moving them from the drive to tape.
Mirror causes the...
Has anyone come across a hardware compatibility list for ARCserve 6.61? CA used to have one at their website, although it was out of date. But now I can't even seem to find that one. I'm looking for any info on ARCserve and EXB-220 and EXB-480 libraries using Mammoth II drives, compatible...
Hi Ka, I had a similar problem when running ARCserve 6.5 (620) on an Exabyte 220 library equipped with Mammoth drives. The backups ran successfully but their were no sessions on the tapes. They had been formatted but no data was written to them. This ended up being an incompatibility with the...
After reading this thread it seems to me that I've seen this behavior before... Although it was with ARCserve 6.5 running build 620 and using Exabyte Mammoth drives. Basically, it appeared that the full back up was successfully run, however when the tape was scanned for sessions there was...
After reading this thread it seems to me that I've seen this behavior before... Although it was with ARCserve 6.5 running build 620 and using Exabyte Mammoth drives. Basically, it appeared that the full back up was successfully run, however when the tape was scanned for sessions there was...
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.