Cyklops -- I have had this problem, too. What is the significance of files in the temp folder? I don't know if I had any, but I might have. This Arcserve backup db is huge -- 15 gb or so.
Durring a backup the backup history to a *.tmp file. At the end of the session it is changed to *.cat and written to the tape at the end of the session. After the job all cat files are merged into the Database. If there are no jobs running and there are tmp files remaining in the ARCserve\temp folder delete them. If there are any remaining cat files try running mergecat.exe to merge them in.
15gb is rather large for a VLDB database but I am not sure it is related to the message in the activity log.
It might be helpful to find out the bounderies of the problem. For instance is it target related?
Check the log to see if it only happens with this one target.
How long is the path?
Doesn't windows have a 256 character length limitation. Perhaps the path to this data is longer.
If this is with the Client Agent try a test backup of just this data without the agent.
These steps should help identify just what the problem is.
Does "local machine" = the ARCserve server?
Or a machine local to the SAN?
The reason for the question is that a local backup does not list the server name as part of the path.
FYI,
CA said, and I have proven, that this is just a mis-report of an error. The backups are not affected. Restores are not compromised.
They have a test fix available, but I am not a beta tester for them. Especially on a production server.
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.