I have a serious problem with Exchange Information Store backup. The last weekend one of the storage log was full, so we had to remove txt log files by hand.
After that, all Incremental backup jobs have failed with status code 4207.
On Monday I sent a full backup job successfully (code status 1, partially copied), but since this weekend till now all incremental jobs have failed.
I've rebooted all services with error status when I send a vssadmin list writers, I've rebooted the entire server, I've changed the node as passive, I've purged the folder ../veritas/netbackup/temp ,... I always get the same error.
Before start the backup job, VSS runs properly (all services are Stable), but after the backup job finishes some services change their status to Error (Microsoft Exchange Writer and Microsoft Exchange Replica Writer). If I stop/start these services they recover the Stable status, but backup jobs fail again.
The Exchange service works properly, the status of DAG seems well:
Name Member Servers Operational Servers
Name Server Recovery ReplicationType
Name Status CopyQueue ReplayQueue LastInspectedLogTime ContentIndex
My Exchange technical support hasn't found problems in the environment.
I don't know what is happening..
Anyone could help me, please?
I attach bpfis and bpresolver logs with debug level 3, and backup job logs.
Are there any Windows event log entries regarding MS Exchange consistency check failing?
If the pre-backup consistency check fails, then no backups are possible.
$ grep "<16>" * bpfis-071515.log:10:00:51.012 [5928.5716] <16> bpfis main: FTL - snapshot creation failed - SNAPSHOT_NOTIFICATION::SnapshotPrepare failed., status 130
...see this TN re status 130 for snapshot for MS Exchange:
Some other posts re same status code: