I concede it could very well be a Windows or Exchange issue - but maybe it is VEEAM not handling the server or something correctly? Any help would be appreciated. My gut is telling me it is something basic I am missing since I'm not having much luck finding other people in the same position. Ran vssadmin list writers and confirmed the existance of the Microsoft Exchange Writer with no errors
Double checked the backup job and confirmed that queiesing is enabled and I have set the advanced settings to truncate the logsĢ. The database is only ~400mb right now.Ī brief list of the troubleshooting steps I've taken thus far:ġ. Our database is very small right now as we have only moved over 3 mailboxes. However, I don't see anything in the windows event log indicating that a successful backup had been run so it should truncate the logs.
The job runs fine and finishes in minutes with no errors. I have configured a new backup job to target one of the Exchange 2010 servers that has a healthy passive copy of our database. We also just upgraded from VEEAM5 to VEEAM6 as we are upgrading to Exchange 2010. We were having a common issue of the DAG failing over because of low default timeout values on the cluster services but I've increased those based on common links I've seen and we haven't had an unnecessary failover in the last couple days now. All three servers are DAG members holding a copy of our single mailbox database. We have (3) Exchange 2010 SP1 RU6 servers running on 2008 R2. We are migrating from Exchange 2003 to 2010 and have our co-existence environment set up.Īll of our VM's are running on the the latest ESX 4.1. I've done a fair amount of searching on both TechNet and the VEEAM forums here and am stumped.
0 kommentar(er)
