In this situation, the memory used by beremote.exe does not drop back down after backup but continues to rise with each mailbox backup performed. Note, I have other systems set up in a similar way that are not affected by this problem. The only difference is that in these cases the backups are not being encrypted. Symantec don’t offer a fix for this problem at the moment, just a workaround. The workaround is to restart the backup exec agent. This could be done via a scheduled task calling a batch file. Basically, the offered solution is a fudge, not a fix. It is, however, very important to encrypt your backups, so turning encryption off is not the solution either – this just avoids the problem. I don’t know if Backup Exec v12 is affected by this issue. I’ve not done enough testing in this version yet. Symantec Tech Support can only offer the fudge and there’s no hint of a fix being released.įor now, the only way forward is to restart the agent when you’re sure the backup process is not in use. So here’s an idea, as an interim solution. Configure the backup job so that it runs a batch file that will restart the backup agent service. To do this, under Job Settings | Pre/Post commands, call a batch file that restarts the remote agent on the remote server. Here’s an example of the command in full: Tip, use the ‘SC.EXE’ command in the batch file.
0 Comments
Leave a Reply. |