Error was actually found in Daemon.log since it was error recorded regarding the communication and since it was finding the incorrect server it was unable to run the nsrsnapck command to delete the snapshot since it just did not find it in the database. .All the best Zlatko..
I understand that the error message you are getting is coming from VSS, and not really from NMM.
I guess you have already some snapshots, and VSS is having issues in applying the snapshot policy, in fact having issues trying to delete old snapshots.
Please run the following command on the Exchange server:
vssadmin list shadows
and also
vssadmin list writers
The first command should return something like:
C:\>vssadmin list shadows
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
If it shows any shadow (snapshot) then you will need to manually delete them, by running diskshadow commands as follows:
Actually, this error is coming from PowerSnap module and you may see it when another RAP deletion operation runs on server. RAP deletetion operations are sequential and usually done on server and under control of nsrd. However, with PowerSnap, this is trigerred by nsrsnapck on client which goes to server and it may clash with NSR deletion operation on server which is progress (like relabeling on tape or nsrim 24h check by server).
After EMC technician looks through a lot of logs and after removing/renaming C:\Program Files\Legato\nsr\res\servers file on both Exchange servers, backups are running fine now. Both Fulls and Incrementals running fine with no problems.
Exchange01 and Exchange02 are storage nodes!
REASON: GSS errors. Exchange01 server assumes that Exchange02 is NetWorker server, and since Exchange02 was not mentioned in "servers" file it just refused to start backups. The same was on Exchange02... it assumes that Exchange01 is NetWorker server. Errors were seen in C:\Program Files\Legato'\nsr\rmagentps\logs folder.
notsure2
1 Message
0
December 16th, 2011 12:00
Error was actually found in Daemon.log since it was error recorded regarding the communication and since it was finding the incorrect server it was unable to run the nsrsnapck command to delete the snapshot since it just did not find it in the database.
.All the best Zlatko..
wmtW1BHxGX12559
1 Rookie
•
100 Posts
0
December 12th, 2011 01:00
Well... strange... after the third restart of Windows and third NMM reinstall, backups are now OK... very strange!
Now, I have to figure out how to restore from those backups.
36115_carloscor
217 Posts
1
December 12th, 2011 02:00
Hello Zlatko,
I understand that the error message you are getting is coming from VSS, and not really from NMM.
I guess you have already some snapshots, and VSS is having issues in applying the snapshot policy, in fact having issues trying to delete old snapshots.
Please run the following command on the Exchange server:
vssadmin list shadows
and also
vssadmin list writers
The first command should return something like:
C:\>vssadmin list shadows
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
No shadow copies present in the system.
If it shows any shadow (snapshot) then you will need to manually delete them, by running diskshadow commands as follows:
C:\>diskshadow
DISKSHADOW>delete shadows all
DISKSHADOW>exit
Let us know if that helps.
Thank you.
Carlos.
wmtW1BHxGX12559
1 Rookie
•
100 Posts
0
December 16th, 2011 00:00
No help with deleting snapshots.
ble1
4 Operator
•
14.4K Posts
0
December 16th, 2011 06:00
Actually, this error is coming from PowerSnap module and you may see it when another RAP deletion operation runs on server. RAP deletetion operations are sequential and usually done on server and under control of nsrd. However, with PowerSnap, this is trigerred by nsrsnapck on client which goes to server and it may clash with NSR deletion operation on server which is progress (like relabeling on tape or nsrim 24h check by server).
wmtW1BHxGX12559
1 Rookie
•
100 Posts
1
December 16th, 2011 12:00
SOLVED:
After EMC technician looks through a lot of logs and after removing/renaming C:\Program Files\Legato\nsr\res\servers file on both Exchange servers, backups are running fine now. Both Fulls and Incrementals running fine with no problems.
Exchange01 and Exchange02 are storage nodes!
REASON: GSS errors. Exchange01 server assumes that Exchange02 is NetWorker server, and since Exchange02 was not mentioned in "servers" file it just refused to start backups. The same was on Exchange02... it assumes that Exchange01 is NetWorker server. Errors were seen in C:\Program Files\Legato'\nsr\rmagentps\logs folder.
wmtW1BHxGX12559
1 Rookie
•
100 Posts
0
December 16th, 2011 13:00
Yes... right... I was confused with so much windows opened...
Thank you again.