Unsolved
This post is more than 5 years old
1 Rookie
•
72 Posts
0
1567
February 22nd, 2013 02:00
Exchange NMM backup fails with failed to commit the replica
My Exchange 2010 DAG backup with NMM 2.4/NW7.6.3.3/W2008R2 fails at the end of the backup.
All log and databases are backup, recovery works.
But backup fail with: error caught calling RM to commit the replica
In the debug logs an other error message can be found:
030255 ERROR: Trying to mount to a cluster node with older replica that does not have sufficient information about the production cluster nodes
No errors in the windows application logs on the DAG nodes.
Transaction logs are not deleted.
I need an idea where to search the reason of this problem.
regards
Bernd
0 events found
No Events found!
nmc2
268 Posts
0
February 26th, 2013 06:00
Bernd,
Please verify is there any error reported in NMM.raw. It will give more idea about the issue.
Attach NMM.raw from client machine if possible.
Regards,
Prajith
CarlosRojas
1.7K Posts
0
February 27th, 2013 03:00
Hi Bernd,
Thah message is not the root cause of the issue.
Please share the nmm.raw and the daemon.raw.
Thank you.
Carlos.
gotschy
1 Rookie
•
72 Posts
0
February 27th, 2013 04:00
File is attached.
All files are backed up and recovery (DB or item) works. But backup is not committed and logs
are not deleted.
regards
Bernd
CarlosRojas
1.7K Posts
0
February 27th, 2013 08:00
Hi Bernd,
Initially backups worked fine, but started to fail on the 29th of January:
024120 WARNING:The transaction logs will be truncated even though the consistency check was not run. Microsoft requires that you check the consistency of Exchange databases and logs to confirm their data integrity. Truncating transaction logs without checking the consistency could result in data loss.
Have you worked with the Exchange admin to ensure the consistency of the DB's.
Have you had the chance to look into the Application, System and Exchange event logs to find out what went wrong?
What I get out of the logs is that NMM is failing to backup the DB's to prevent you to have a non consistent backup however to be sure 100% I would need to see the application and Exchange logs, but is complicated to attach those here, so please take a look around the date backups started to fail and I'm sure you will find the problem in there.
Also I suppose that writers are in correct status, right?
Thank you.
Carlos