Veritas Backup Exec 20.6 and Exchange 2013 CU23 Backup
Hi! Backup does not work on some databases at the same time without any regularity. The backup copy itself performs quickly. Then it hangs for a very long time. Background process. Turned on debug and saw the following. Resource and files are accessible and open.2.6KViews0likes7Comments
Please update Article ID:100023134
I had an issue where my VSS Microsoft Exchange Writer was missing from the VSSADMIN.EXE LIST WRITERS command. When viewing article ID:100023134, section VSSADMIN Commands, it reccomended restarting the Exchange Information Store service. This did not work. According to microsoft documentation starting in Exchange 2013 the VSS writer was moved to the Exchange Replication service. Therefore, please update Article ID:100023134 to reccomend restarting the Exchange Replication service in addition to restarting the Exchange Information Store service.Solved1.4KViews0likes3Comments
Exchange 2013 database restore successful - but database not mountable / dirty shutdown
Hi, Currently testing disaster recovery of an exchange 2013 server with Backup Exec 2014. Backup job taken successfully with BE Windows Agent. Successfully restored the server into a VM using SDR. Afterwards restored Exchange database and logfiles to original location. Instructed BE to overwrite existing. The Exchange restore job is successful - but store is not mounted automatically. Manual mount not possible - getting dirty shutdown error code. Have tried soft repair with eseutil - but it fails and reports that some logfiles are missing. Only option that works is hard repair - but my logfiles should be OK.. 1. Circular logging is disbled on the production server 2. No other backup software in used for Exchange backup - that could possibly interfere with the logfiles /flush them. 3. Log files are flushed correctly after each full backup job What am I missing here? We run full backup job each friday and differential other days. Differentials are logfiles only (logfiles not deleted until after successful full backup) Could there be an inconsistency in my Exchange database that could cause the replaying of log files to fails - or am I just doing the restore wrong? Regards ThomasSolved1.8KViews0likes4Comments
Veritas Backup Exec 20.6 and Exchange 2013 CU23 Backup
Hi! Backup does not work on some databases at the same time without any regularity. The backup copy itself performs quickly. Then it hangs for a very long time. Background process. Turned on debug and saw the following. Resource and files are accessible and open.