If these are in fact missing from your nsrinfo output (for the database in question), then we will need to try a few different steps to re-populate that data. We need to ensure that we see "Metadata KEY" entries for the dates in question. Once this command finishes, open the text file and find entries for the date that you have chosen for restore. This will dump the contents of the index to this text file we specify. We can check this by running the following command on the NetWorker Server: " nsrinfo DAG_HOSTNAME > c:\temp\nsrinfo.txt". If all of the savesets appear to be browsable, then this may be an issue with the client's index missing certain entries. Let me know if you need a hand with confirming this.
The XML saveset would need to show as at least Recoverable. The savesets that need to show as Browsable would be the " APPLICATIONS:\Microsoft Exchange #", and " VSS:\".
CONTENT INDEX STATE FAILED EXCHANGE 2010 FULL
It could be occurring if some of the savesets are not marked as 'browsable', or could also occur if certain entries in the index are missing.Ĭould you confirm that all of the required savesets are listed as Browsable? Depending on the date you are selecting, this would be the most recent Full backup from that time, as well as any subsequent incrementals. With the Passive Copies of the two DB's on the same exchange server, why is one failing and the other not.I've seen this error occur when the Client File Index is not properly updated for the date you are trying to restore. 50Mbps MetroE connectivity or not, it'll still be slow. I'm not backing up the active db over a WAN link. This is not an option, as the passive database copy and the backup server are in the same data center, with the active copy being in the client main office.
Symantec Tech Support's initial fix was to email me this technote: which states the solution is to backup only the Active Database Copy. The Backup Exec Job fails with: V-79-57344-862 - The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database. The VSS errors state: The VSS Writer failed, but the operation can be retried (0x800423f3)
CONTENT INDEX STATE FAILED EXCHANGE 2010 INSTALL
Recently, my Backup Exec 2012 SP1a install has been receiving failures from 1 of my 2 Exchange 2010 databases under DAG.