Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

938

February 4th, 2014 09:00

nsrsnap_vss_save does not collect new names of Exchange Storage Groups

Dear all,

Need some guidelines on following problem.

Environment:

Exchange 2007

Networker server 8.0.2.3

nmm.241.Build.122

After renaming storage groups on Exchange server the backup fails with error message in nmm.raw below:

02/04/14 07:03:33  spng103.dubdpng.local nsrsnap_vss_save Exchange storage group SG3 on server SPNG103 log file path and system file path do not match.  Terminating backup.

Strange thing is that storage group "SG3" is the old name of storage group and it does not show up in Exchange management console.

The log file path and system file path are the same for the storage group SG_Franzis_1 (which is storage group the SG3 has been renamed to).

Here is the excerpt from output of 'nsrsnap_vss_save -G' demonstrating, that nsrsnap_vss_save collects old SG names:

caption='SG_Fachmedien_1'

caption='Logs'

caption='Fachmedien_01_SPNG103'

caption='SG_Fachmedien_2'

caption='Logs'

caption='Fachmedien_02_SPNG103'

caption='SG1'                         << SG_PublicFolder(in Exchange Managment Console)

caption='Logs'

caption='PublicFolder_SPNG103'

caption='SG3'                         << SG_Franzis_1 (in Exchange Managment Console)

caption='Logs'

caption='Franzis_01_SPNG103'

caption='SG4'                          << SG_MediaPublishing_1 (in Exchange Managment Console)

caption='Logs'

caption='MediaPublishing_01_SPNG103'

Storage groups with new names are shown up in Exchange management console:

201402041813.png

The 'nsrsnap_vss_save -?' shows old names (SG1, SG3, SG4):

201402041219.png

Any idea, how to make nsrsnap_vss_save to collect "actual" data?

Thanks.

4 Operator

 • 

1.3K Posts

February 4th, 2014 23:00

I am assuming the information passed on to the nsrsnap_vss-save by the exchange writers still holds the old information !! was the server rebooted after the migration? If not, can you consult with you exchange admin if they can restart the 'Microsoft Exchange Replica Writer" service on the exchange ?

14 Posts

February 5th, 2014 08:00

The problem was resolved onsite by the customer.

Unfortunately there is no information on how it was fixed.

Anyway thanks a lot for help.

No Events found!

Top