#BACKUP EXEC 2010 AGENT SOFTWARE#
General installation is a swift process and an optional environment check scans the server to ensure that it meets the minimum hardware and software requirements.
#BACKUP EXEC 2010 AGENT WINDOWS 7#
These may be delayed if a shadow copy is being prepared.Other new features are support for Server 2008 R2 as a media server and the Core version as a client, a remote agent for Windows 7 and a greater focus on virtualisation with support for vSphere 4.0 and VMware incremental backups.įor testing, we loaded Backup Exec 2010 on a Broadberry CyberServe rack server equipped with dual 2.8GHz X5560 Xeons and 6GB of DDR3 memory. Share the writers status - Its looks like. ALso let me know your OS Versions and CAS /MBX server role details. This can be beneficial to other community members reading the threadĬan you provide us some cluster logs for more clear view on this case. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
The only advice I can give is to make sure the the Cluster IP is resource is running on which ever server is currently holding the PAM role. Or you can look at their log files, I'm sure they have something you can review. Your best bet would be to call Symantec so they can tell you what call is failing and why. Backup exec has started to perform the backup successfully. I have rebooted the witness server again as the server is where the backup exec installed. As checked, all DAG are working perfectly between nodes and all of them are mounted successfully. Let me try to reboot the witness server again and see how. Get-MailboxDatabaseCopyStatus -Server testmb01 The status of the DAG after performing the command below is all Mounted and Index is healthy I have checked that the DAG is actually working and the HDD size is more than enough. If you have feedback for TechNet Support, contact Xu Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. In addition, check if there are any errors in application log and post them for our troubleshooting. Then, check the size of backup hard disk to check if the size is not enough.
Notice: this link also apply to Exchange 2010.
Please make sure DAG replication in DAG 1 by the following link, if there are any error, you could post them for our troubleshooting. I really not sure what is happening here as the issue come when I rebooted the backup server which contain the witness server due to some backup error few days ago and I think it won't have this funny effect. Working fine and doesn't seem to have issue too. From here, the issue should not with the Backup server right? but, the "DAG" cluster is currently I have tried to backup the other DAG cluster called "DAG2" and "DAG3" and it is able to work using the same backup exec server. the error message is misleading because I can confirm that the backup account that use to backup is part of the Exchange Trusted Subsystem and the account is not locked at all. I am sure that the cluster is running because it is able to failover to the other nodes when one of the nodes member is down.īelow is the error message from the backup exec. Ensure that the cluster is running and not in the failed state. restart the services of Microsoft information store on all exchange servers.Ĥ. Rebooted all exchange servers involved in the DAG clusters and ensure that the backup exec services is running on all servers.ģ. To work even though the version is slightly different.Ģ. for this, I have upgraded the remote servers (4 exchange servers) backup exec agent to the same version as the backup exec media server. Ensure the backup exec on the media server has the same version with all remote servers. Recognize the Microsoft information store of the DAG cluster, hence I am not able to backup the exchange database.ġ. The backup is working fine till suddenly these few days, the backup exec failed to the 4 servers has been member of the DAG cluster called "DAG". witness server is justĪ normal server and not part of the exchange server, however it is part of the my backup exec server. there is DAG configured for my all exchange servers. My exchange server is running on exchange server 2010 SP1. I am currently using backup exec 2010 R3 to do a backup for my exchange server.
0 kommentar(er)
