savegrp: suppressed 4 lines of verbose output
63372:nsrsnap_vss_save:NMM .. Registration of snapshot set failed -- NMM .. Operation unit failed with error Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[..........] and the proxy client[...] NetWorker Server [....
77175:nsrsnap_vss_save:NMM .. completed commit replica with status of false.
63335:nsrsnap_vss_save:NMM backup failed to complete successfully.
68151 1345369024 2 0 0 700 10720 0.... nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
rker Module for Microsoft Applications,
As I see the above error does not give more information about the problem.
But I doubt that the issue is between the host and the client machine which are having problems in communicating with each other.
Please check if there is any DNS issues. Ensure that they are able to ping each other
Perform a nslookup and reverse look up and see if the names are getting resolved.
Please give us more information about the following:
1. Networker running on the server 2. NMM version on the client 3. Attach the nmm.raw from the client machine
This is a very popular issue which was in fact discussed in previous posts.
This is usually caused by one of the following reasons:
1.- Name resolution issue (check nslookup forward and reverse resolution)
2.- Configuration issues (check snapshot group, pool, devices etc)
3.- Client ID/Nested indexes issue (in this case I would suggest you to engage support)
Anyway check carefully the names specified in the error message, and ensure that the Proxy host and the Application host aliases are the same (they should be as both are the same machine unless you are using Proxy host backups, which I don't think so) and that the name is included exactly as written in the error message within the alias field of the client.
Also ensure that the name of the backup server is correct.
We are getting frequent exchange backup failure.
We found exchange writer is in retryable state, We restarted Microsoft exchange information store but still exists.
Today we found there is no exchange writer on server.
And backup is failing with error parameter incorrect.
If there is no writer present that is an issue at Exchange and Os level, nothing to do with NetWorker or NMM.
Please engage your Exchange admins to find out why the Exchange writer is not present, most likely some permissions issue.
You can check the Application and System event logs and I'm sure you will find the answer in there.
Thank you for your input, but we have not seen any error messages regarding exchange writer.
Our exchange client recently deleted one DB after that we missed that exchange writer.
Can we add exchange DWORD or need to do any changed from exchange end.
Could you help me out.
We got failed again, below is the error message.
Could any one help me out.
NMM .. cluster failover or application role change after a replica created may have caused snapshot creation failure, try to restart the backup.
A deletion of a DB shouldn't cause Exchange writer to disappear. Can you please attach the output of the following command ran on the 2 DAG nodes please?:
vssadmin list writers
vssadmin list snapshots
Actually forgot to ask, is this a cluster or a stand-alone server?
I'm confused, as you said:
"Today we found there is no exchange writer on server."
But I can see the Exchange writer present in the output of the vssadmin list writers command.
I also see there is one snapshot present, so if there is no backup in progress please delete that snapshot.
To do it run the following commands:
From the DISKSHADOW prompt type:
delete shadows all
Then exit from DISKSHADOW prompt.
Exchange writer is in stable status, so you are good to start a new backup.
I don't have any information as of what is the failure you get, as this thread wass opened by a very specific failure, so can you please provide me with some more information, and if possible attach the nmm.raw file here?
Please try to open new questions in the forum instead of using existing ones, as this could lead to confusions.