Highlighted
nadar1
1 Copper

EMC Networker Exchange 2010 backup failing with VSS Error

Hi All,

I am totally new to EMC Networker, I am facing an issue while taking a backup of Exchange, I am pasting the error details below, I like to know it is a host related issue or networker related and resolve it. Please help me on this.

APPLICATIONS:\Microsoft Exchange 2010: Backup of [APPLICATIONS:\Microsoft Exchange 2010] failed

ave:RM .. 027288 ERROR:A VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED error occurred while adding volumes to the VSS snapshot set. The error code is: 0x80042312.

49931:nsrsnap_vss_save:RM .. 026084 ERRORSmiley Frustratedtorage Services operation processExecute failed with an error as follows: Storage Services has terminated with an error.

49931:nsrsnap_vss_save:RM .. 027286 ERROR:A VSS_E_OBJECT_NOT_FOUND error occurred while deleting the VSS snapshot set. The error code is: 0x80042308.

49931:nsrsnap_vss_save:RM .. 027114 ERROR:Exchange Information Store is stable. The error is VSS_UNKNOWN_ERROR.  The code is: 0x00000000. Check the application event log for more information.

49931:nsrsnap_vss_save:RM .. 027114 ERROR:Exchange Information Store is stable. The error is VSS_UNKNOWN_ERROR.  The code is: 0x00000000. Check the application event log for more information.

49931:nsrsnap_vss_save:RM .. 027114 ERROR:Exchange Information Store is stable. The error is VSS_UNKNOWN_ERROR.  The code is: 0x00000000. Check the application event log for more information.

Microsoft DiskPart version 6.1.7601

Copyright (C) 1999-2008 Microsoft Corporation.

On computer: xyz

Automatic mounting of new volumes disabled.

Microsoft DiskPart version 6.1.7601

Copyright (C) 1999-2008 Microsoft Corporation.

On computer: xyz

Automatic mounting of new volumes disabled.

37959:nsrsnap_vss_save:The group or resource is not in the correct state to perform the requested operation.

.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

68151 1502302733 2 0 0 6544 4632 0 xyz.local nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0

Labels (1)
0 Kudos
6 Replies
bingo.1
3 Cadmium

Re: EMC Networker Exchange 2010 backup failing with VSS Error

The code clearly indicates what it already explains verbally: "error occurred while adding volumes to the VSS snapshot set"

   You should run "diskshadow list shadows all" to see why you have so many shadows.

Make sure that the config check during the NMM installation runs fine.


0 Kudos
ble1
5 Iridium

Re: EMC Networker Exchange 2010 backup failing with VSS Error

It starts with ERROR:A VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED.  In the past I think it was 64 copies you could have... (see In VSS, how to take a snapshot containing more than 64 volumes at a time?)

nadar1
1 Copper

Re: EMC Networker Exchange 2010 backup failing with VSS Error

Thanks for your valuable input, Actually my infrastructure is a full VM environment. In the same Networker group other clients are also their,  Correct me if i am wrong, As per my understanding the Exchange  2010 server has more  than 64 volumes, hence error occurred while adding to the VSS snapshot set. How can i suggest to windows team on this

0 Kudos
bingo.1
3 Cadmium

Re: EMC Networker Exchange 2010 backup failing with VSS Error

Correct about the number of volumes. Such number is absolute unusual.

As we do not know your environment, it is hard to make good statements here.

You better bring the Exchange and the VMware admins together and let them the next optimization steps.

nadar1
1 Copper

Re: EMC Networker Exchange 2010 backup failing with VSS Error

Now backup is happening fine,Windows team fixed it by fine tuning the exchange server. As their is an issue while reading data from exchange database to VSS, its fixed by wintel team. will update further on this if i get more details

0 Kudos
nadar1
1 Copper

Re: EMC Networker Exchange 2010 backup failing with VSS Error

Actually windows team updated in comments: Cleared the temp *.cab file from C drive, and did the redistribution of DB data, it may have resolved the issue