NMM 2.3 Exchange 2010 DAG database recover to RDB failed

Hello Herman,

This problem can be caused for 2 reasons:

1.- VSS:\ saveset (cover set) is missing or not browsable

2.- Indexes or any other saveset for the backup of that client are not available/browsable.

Basically it is failing because cannot restore the metadata, so if metadata is not restores NMM won't be able to find out the writer information so it won't be able to restore.

Please check in NMC the savesets available, and its status for DAG client name. You should see the index saveset, the VSS:\ saveset, the Metadata (.xml file, name should be something like: C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT1317994217.xml) and at least 2 savesets with name APPLICAITONS:\Microsoft Exchange 2010.

If any of these is not browsable please scan the volume in.

Also, are you trying to restore from original backup or clone?

Thank you.

Carlos.

Thanks for your reply.

When i take a look within the NMC indexes i see the following savesets:

{ DAG name} client  :

APPLICATIONS:\Microsoft Exchange 2010\DB01

APPLICATIONS:\Microsoft Exchange 2010\DB02

VSS:/

DAG Client 1:

No savesets

DAG Client 2:

No savesets

----------------

Is this correct ?

Hi Herman,

That is the problem, you don't have a valid saveset for the metadata.

Please note that NMM will restore first the metadata, so it can read it and gather the required information about the snapshot to be restored, the writer and files to be restored. If there is no metadata NMM won't be able to restore.

You are missing the file C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT1317994217.xml

Is this an original backup or a clone?

could you try to run a new backup and let's see if you can restore afterwards?

Thank you.

Carlos.

Hi Herman,

From the error messages given I would say you're facing problems with Windows 2008 UAC.

Please try to start the NMM user GUI with "run as administrator".

I assume you have all the rights needed assigned to the logon account already.

Regards,

Guenter

When i start a backup session  , i can see that C:\ProgramData\EMC\NetWorker\LG....xml is backuped to tape.

Your collegue Guenter had also a reply to me becaude i made also a service request. , his suggestion was to start NMM user GUI on the DAG client as administrator.

I did that and now the restore to the RDB database works fine.

But when i want to recover a single mailbox i get the following error:

Starting Exchange recover using C:\Program Files\Legato\nsr\bin\nsrxchmbrc.exe -s as18.gdvdieren.intern -c MBX02 -t "Mon Oct 10 14:59:50 2011" -g {c0b170aa-555e-4591-86c5-6d19e1023557} -I -

The following 1 marked items are being recovered:

MSEXCH:RDB/%2FO=GD%2FOU=FIRST ADMINISTRATIVE GROUP%2FCN=RECIPIENTS%2FCN=TESTUSER2/

20494:nsrxchmbrc:No authority for recover operation

43709:nsrxchmbrc:Stop time: Mon Oct 10 15:00:46 2011

Recover program exited with status: 1244

The options specified in the Recover Options Dialog have been reset back to their safe default values.

---------------------------

Any Idea ?

Hello Guenther,

Thanks for your reply, when i start NMM as an administrator i can restore a database to a rdb database.

Regards,

Herman.

Carlos,

Everything works fine at the moment i can restore a database to a rdb database and i can also recover mailbox/foler or email.

Thanks.

Regards,

Herman.

Hello Carlos,

After some restoretests we want to restore again a database to a rdb , but now we get an error:

----------------------------------------------------

63500 18-10-2011 14:50:15  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover NMM .. calling VSS PreRestore.

63474 18-10-2011 14:50:15  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover NMM .. Gathering writer status  after PreRestore... 

66422 18-10-2011 14:50:16  2 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover NMM .. gather writer status  after PreRestore returned status failure VSS_WS_FAILED_AT_PRE_RESTORE for writer 'Microsoft Exchange Writer'.  Writer failure 0x800423f3 -- VSS_E_WRITERERROR_RETRYABLE 

79780 18-10-2011 14:50:16  5 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover NMM .. After PreRestore ... writer status indicates a failure -- 0x800423f3, check the Windows event logs for possible VSS related errors.

64714 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover NMM .. XML file for recovery savetime 1318925166 has been saved to C:\Users\serviceex2010backup\AppData\Local\Temp\vssclient_18144828553.xml.

67472 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover NMM .. successfully deleting the old XML files that are older than 30 days.

71234 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover **************************************************************\n\n

71235 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  

71238 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  Recover completion status 

71235 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  

50247 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  VSS validation and preprocessing failed for Microsoft Exchange 2010 with error 0x800423f3. 

71235 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  

50247 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  Restore completed with an error for Exchange DB02. 

71235 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  

56473 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover **************************************************************

71235 18-10-2011 14:50:16  1 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover  

50322 18-10-2011 14:50:21  0 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover nsrsnap_vss_recover: vssClientRestore() failed.

79782 18-10-2011 14:50:21  0 0 0 2872 6380 0 mbx02.gdvdieren.intern nsrsnap_vss_recover nsrsnap_vss_recover: Recovery operation failed.  Refer to log file(s) and Windows event logs for details.

-----------------------------------------------------

Any idea ?

In last instance you see that VSS Exchange writer return error.  If you have done vss list writers you would most likely see retryable error status next to it.  As for why, you will need to check event log (even though that might also not give answers).

exchange recovery corrupted/unreadable exchange folders, messages and rest data are damaged by power shortages or surges, physical damage and incorrect user's actions. Program finds out, analyzes and restore crashed exchange data. It uses step-by-step wizard, which allows you to control the recovery options and go back any time to make the necessary changes.

Herman and Alex

Were you able to carry out the restore then?

Thank you.

Carlos.