NMM : failed to create place holder file ????

You can do a test (I would suggest to do it in a NON-PRODUCTION box):

let's say you have Exchange installed on that box. Install then NW client and NMM 2.3 on top of it.

Then run nsrsnap_vss_save -v -?

If everything is correctly configured etc this will show the valid Exchange DB's to be backed up, with the correct saveset name.

Then open command prompt and run this on the exchange box:

nsradmin -p nsrexec

nsradmin>option hidden: on

nsradmin>. type: nsrladb

nsradmin>print

This will display all client information, including the ID for each of the writers.

Then you can uninstall NW client (uninstall, not repair) and then install it again.

Follow the same procedure again and let me know if you are missing any writer information

Thank you.

Carlos.

Hi Jeje,

nsrsnap_vss_Save -G is explained in the documentation. Please see below:

NMM provides a command to dump the VSS writer metadata to XML files. These

XML files detail what each active writer on the system is doing, and may be useful to

support personnel for investigating and analyzing writer issues.

To dump the VSS Writer metadata to XML files, run the nsrsnap_vss_save command

with the -G command switch, for example:

D:\Legato\nsr\bin>nsrsnap_vss_save -G

This is useful for advanced troubleshooting.

In regards to vssclupdate, it basically updates the VSS information of that particular client.

Let me explain it better, if you install NW 7.6.x, and then NMM 2.3, if for whatever reason you need to update the NW client software, and you do it without uninstalling NMM, then the reinstallation of the NW client software will overwrite C:\Program Files\Legato\nsr\nsrladb

That folder contains the NW client information/configuration/security files. NMM relies on that client information to gather the application installed on that client that is going to be backed up (the list of VSS writers), so basically vssclupdate will repopulate all the writers for that client, so when you run nsrsnap_vss_save -v -? again it will display all the correct and valid savesets, and that will also correct some other backup related issues as the one mentioned in this post.

Thank you.

Carlos.

Hi carlos am also facing same issue and it is not standalone because when i check the client which failed in that hostname is different.

and i have checked "vssadmin list writers" also no error is found, please update me resolutions to make it successful.

Error:

APPLICATIONS:\SqlServerWriter\LHRSQL040D: Backup of [APPLICATIONS:\SqlServerWriter\LHRSQL040D] failed

vss type System Service - NMM saveset type SYSTEM COMPONENTS.

Checking name is valid or notExecution in check_valid_name save set name APPLICATIONS:\SqlServerWriter\LHRSQL040DComparing APPLICATIONS with save set name APPLICATIONS:\SqlServerWriter\LHRSQL040D82624:nsrsnap_vss_save:Save set name APPLICATIONS:\SqlServerWriter\LHRSQL040D is valid.

NMM .. created RM deposit path C:\Windows\TEMP\RMDir_2921116620.

63352:nsrsnap_vss_save:NMM .. start the creation of a replica. Replica will be of type Default - which is VSS determined  Non Transportable.

83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation.  Details in nmm.raw on lhrsql040d.uk.baa.com and in the Windows Application or System Event Log.

49931:nsrsnap_vss_save:RM .. 100722 ERROR:waiting 1200 seconds for DoSnapshotSet to complete. DoSnapshotSet was cancelled

49931:nsrsnap_vss_save:RM .. 026202 ERROR: Storage Services operation waitVSSCompletion failed with an error as follows: Wait Snapshot completion failed.

49931:nsrsnap_vss_save:RM .. 026084 ERROR:Storage 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 .. 027121 ERROR:SQL Server 2008:SQLWriter has failed at prepare snapshot. The error is VSS_E_WRITER_NOT_RESPONDING.  The code is: 0x80042319. Check the application event log for more information.

NMM .. ending RM session.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

nsrsnap_vss_save(380): Entering SendRecoverJobFailure().

Internal error.

nsrsnap_vss_save(392): Exiting SendBackupJobFailure().

nsrsnap_vss_save: Sending backup status to nsrsnap

68151 1483046503 2 0 0 20324 22820 0 lhrsql040b.uk.baa.com nsrsnap_vss_save NSR warning 39 nsrsnap_vss_save: Exiting with failure. 0