1.7K Posts

September 11th, 2014 06:00

Hello,

Do the following:

1.- Delete the peer information of server from client and of client from server, to do it so, you can run the following commands from the server:

nsrdmin -p nsrexec

nsradmin>. type: nsr peer information

delete name: client_name

delete?y

nsradmin>quit

This will remove the peer information of the client from the server.

To delete the peer information of the server form the client, type form NW server:

nsradmin p nsrexec -s client_name

nsradmin>. type: nsr peer information

delete name: nw_server_bame

delete?y

nsradmin>quit

Try again, and if you are not yet able to display the valid savesets then please do as follows:

From Exchange server, in the command line, go to the bin directory where NMM is installed (By default C:\Program Files\EMC NetWorker\nsr\bin), and run these commands:

nsrnmmexchra -u

They run this command:

vssclupdate

Then run this command:

nsrnmmexchra -i

Thank you,

Carlos

1.7K Posts

September 11th, 2014 06:00

On the other hand I see nsrsnap_vss_save command command.

Please check your application and event logs, as most likely you will find either some permissions related error messages or something rwlated to IIS.

Thank you,

Carlos

1.7K Posts

September 11th, 2014 06:00

Do you get the same output if you run the same command (changing the physical node name) in both nodes?

Can you please run the following command in both nodes and attach the output?:

nsrsnap_vss_save -D5v -c physical_node_1 -A NSR_VIRT_SERV=virtual_node -v -?

and

nsrsnap_vss_save -D5v -c physical_node_2 -A NSR_VIRT_SERV=virtual_node -v -?

Thank you,

Carlos

268 Posts

September 11th, 2014 06:00

Have you tried configuring backup manually without using wizard? See if it works.

Also i would suggest you to look at the nmm.raw, it might have some error message related to this.

2 Posts

September 12th, 2014 02:00

Hi, Carlos!

nsr peer information delete commands I have done previously

(there was a auth problem, because of the recent reinstallation server the NW-server, I guess)

BUT,

These cmds fixed this issue! (I ran them on both servers)

nsrnmmexchra -u

They run this command:

vssclupdate

Then run this command:

nsrnmmexchra -i


Thank you!!!


No Events found!

Top