We contacted Symantec and they provided us with this hotfix yet the problem still occurred. Symantec Backup Exec Remote Agent for Windows Servers. Go to your Vmware Manager and edit the particular Virtual Machine that runs Backup Exec. This will allow you to modify the accounts credentials. If the account does exist, then select the account and click Edit. Next, check to see if a system logon account exists. For Backup Exec 11.x and 12.x, type cd C:Program FilesSymantecBackup Exec 4. To fix the problem, open Backup Exec and go to Configuration and Settings > Logon Accounts > Manage Logon Accounts.
For Backup Exec 9.x and 10.x, type cd C:Program FilesVERITASBackup ExecNT 3. Click Start Run, type CMD, and click OK 2. Do this until Backup Exec is completely up to date. Here are the steps to start and stop the BE services using bemcmd.exe from the command prompt. Exchange shows mailbox databases are healthy and mounted. Backup Exec is set to backup the active (local) copy on the primary site. Exchange is setup in a DAG connected by a high speed WAN link.
Ensure that Anti-virus scanning is disabled for Backup Exec folder (excluded) Thanks,-Sush. Also finally try to perform a REPAIR installation of Backup Exec from Add/Remove Programs. May be BE is installed on some other location.
We're trying to do a back up of the exchange storage groups using Backup Exec 2010 version 13.0 (With AOFO disabled) however, we're receivingĪn error "Snapshot provider error (0圎000FED1): A failure occurred querying the Writer status." Install Backup Exec on the Virtual Machine that you would like to be the Media Server, run updates then restart server. Ive been having some trouble getting My Exchange 2010 SP1 backups working. Go to properties of any BE service and check the path it is showing where the executable is present. We're running Exchange Server 2007 version .002 on a Sever 2003 圆4 SP2 system.