Posting is provided "AS IS" with no warranties or guarantees, and confers no rights. Since you are using Symantec Backup Exec for backups, I would recommend asking them in Symantec forums. Backup Exec 2010 R3 Exchange mailbox restore issues J03:59AM Hi Mitch, thank you for your reply, i have just checked the BE server is fully updated, there are no more updates coming up in the LiveUpdate the Server agents were also up to date, just to be safe i re-installed them all and restarted. Has anyone come across this before? Any advice much appreciated. From what I have looked up it seems like a routing issue. I sent some test results back to Symantec and was given the following reason for the problem: Network path does not properly support PMTU discovery. My first attempt will be to try backing up the passive copy of MailDB at the secondary site. So at work we use BE 2010 R3 and have been getting dreadful disk to disk write speeds. The same server has backup exec 2010 r3sp1 installed on it and as far as i know should not need to have the remote agent installed on. The same backup without activating ADBO runs fine with no errors. VSS Admin List Writers on Exchange shows 0 errors and only uses the default Microsoft VSS writers. snapshot backups via backup exec 2010 r3 fail I am trying to set up backups to use the san snapshots for zero impact during production days. Symantec Backup Exec displays the error message "failure querying the writer status", which according to Symantec support is a general error message.
#BACKUP EXEC 2010 R3 SP4 CODE#
The aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a database before a previous backup attempt had fully terminated.)Įxchange VSS Writer (instance 542dc4c9-c31d-4316-8ef8-75a4afe458c1:44) failed with error code -2403 when preparing the database engine for backup of database 'MailDB'. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect
#BACKUP EXEC 2010 R3 SP4 UPGRADE#
The message on Exchange I get in the event logs are (The previous mail backup attempt occurred 24hrs ago):Īn attempt to prepare the database 'MailDB' for backup failed because the database is already in the process of being backed up. I understand that 2010 version is EOL but at the moment upgrade is not possible.
There are several mailboxes within my DAG, but 1 consistently BackupExec 2010 R3 SP4 on Windows 2008 R2 with SQL Server. Supported platforms include VMware and Hyper-V virtualization, Windows and Linux operating systems, Amazon S3, Microsoft. A search at Symantec Website didn’t produce the right results.
#BACKUP EXEC 2010 R3 SP4 SOFTWARE#
Exchange shows mailbox databases are healthy and mounted. Veritas Backup Exec is a data protection software product designed for customers who have mixed physical and virtual environments, and who are moving to public cloud services. Backup Exec is set to backup the active (local) copy on the primary site. Both servers are 2008 R2 64 bit.Įxchange is setup in a DAG connected by a high speed WAN link. I've been having some trouble getting My Exchange 2010 SP1 backups working. Well if you have got to this page you probably already have backups running to disk (and duplicate to tape) via the VCenter using AVVI and your looking to turbo charge your backups.
0 kommentar(er)
