Remote agent verify very slow.
Updated: 06 Dec 2010 | 6 comments
This issue has been solved. See solution.
We are running 11d 7170 SP4 on windows server 2k3.
Having intermittent problem with verify taking a long time to run. The backup portion of the job appears to run fine. All the jobs are to disk not tape. Jobs that normally take 30 minutes for backup and verify suddenly take 3-4 hours. The jobs do complete if I let them run long enough.
We have verified the agents are the correct versions. Also the backup to disk drive has been defragmented. The problem just keeps coming back. I have not been able to pin point any trigger for the problem.
Discussion Filed Under:
Comments
RE: Remote agent verify very slow.
And this is only for Remote backups? Do local verifies ever run slow?
Reason I ask is that Verify does NOT access the original data location and compare backed up data to 'live" data 9a rather useless exercise on an active server, right?)
What verify does is read the backed up data, compute checksums and compare those to checksums written into the backup. If they match, the backed up data "verifies"
Is any other process running against the drive when the verify runs slowly? AV Scan for example
If this response answers your concern, please mark it as a "solution"
Other processes running on the drive.
The only processes running at that time should be the verify. These are WinXP backups which are showing this issue. All my Win2K3 servers seem to run the verify process fine. It is just such an odd issue. I scheduled four WinXP backups for this morning. Two of them ran fine and took about 30-45 minutes. The other two took almost five hours. They are scheduled to run 30 minutes apart.
You already tried a very good
You already tried a very good step of defragmenting it. Can you please try a remote B2D or a different removable disk as it might be the issue with the disk itself.
I have seen this issue and defrag mostrly resolved the issue but you have already did the defrag.
Resolved
It appears to have been the Symantec Endpoint Protection. When the B2D folder was excluded from scanning the problem went away.
Dont forget SEP also needs to
Dont forget SEP also needs to be configured to not scan the SQL database, the installation dir of BE, and the running process beremote.exe too. There is a support topic on what needs to be excluded.
There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."
I've just looked for this,
I've just looked for this, and I can find one about "Best practices for Backup Exec 12 and Symantec Endpoint Protection", but this is about ensuring the two products integrate well. The Backup Exec Administrator's Guide doesn't give much information either.
Have you got a link?
http://www.backupexecfaq.com
Would you like to reply?
Login or Register to post your comment.