Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ArcserveIT 6.6 skipped files as "open files"

Status
Not open for further replies.

ITSlave

Technical User
Apr 27, 2000
1
US
I am using ARCserveIT 6.6 on netware 4.11 with SP6 installed.<br><br>The DLT backup was initiated last few nites where no one was in the office ...<br><br>Surprisingly I was told that more than 80% of files in each volume was not backup. Reason is they are all &quot;Open Files&quot;, which are actually closed during the nite.<br><br>It was OK with previous version ?!?!
 
We are having the same problem with Arcserve 6.6 and Netware 5.0. We have run backups on this machine many times with no problems. This just started happening a month ago. We are going to try the &quot;open files agent&quot; as a temporary fix.

We have another backup server with Arcserve 7.0 on Netware 5.1. We tried to backup the above server but had the same problem so it's definately the target server that has the problem.

I'll let you know if we find anything out. Please post if you find a solution.
 
With both my Arcserve 6.61 and Arcserve 2000 set-up I have to select under options in the backup menu &quot;Deny Write&quot;(The third selction of the four) and not the default Use Lock after Deny write fails(the first option), it make no sense since it should try Deny write first anyways but after I made this change no more skipped files(unless they were truely open)

Regards,
Mike
 
Well, if you use deny write, if the program denies ARCserve the ability to deny write, then the file will not be backed up. By default it should be deny none. It should be on &quot;use lock mode if deny write fails&quot;, because then ARCserve will lock the file if the file denies the deny write action.

hehe hope it's not too confusing.

g
 
We've already checked into all the &quot;deny&quot; options. We currently have a backup server and backup this problem server remotely. As a test, we loaded Arcserve locally to that machine and finally got a successful backup. It looks like the problem is related to the communication between this problem box and any remote backup server. I will post with any updates.
 
Are you using any agents to backup remotely? -----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------
 
also, have you made sure your rights are fully set for the security config of the job?

Domain admin, backup operator rights... etc..?

g
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top