Unsolved
This post is more than 5 years old
22 Posts
0
1314
May 26th, 2016 14:00
Error encountered performing snapshot import: PS .. Error completing snapshot import
Hi,
Can any one help me to fix this issue? Backup getting failed in DAG environment last two days, Previously it was fine but now its getting failed with following error.
80245 5/26/2016 4:34:39 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. checkFor447Errors = 1, checkFor448Errors = 1, DAG Name [SBP-DAG01].
69892 5/26/2016 4:34:39 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. singleThreadEseUtil = 1, throttleEseutil = 1, throttleIos = 100, throttleDuration = 1000
63773 5/26/2016 4:34:39 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. Writer Microsoft Exchange Replica Writer comp File was not explicitly added to backup\n.
63773 5/26/2016 4:34:39 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. Writer Microsoft Exchange Replica Writer comp Logs was not explicitly added to backup\n.
63794 5/26/2016 4:34:39 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. added Microsoft Exchange Replica Writer - EX3-DB2 to RM replica list.
62959 5/26/2016 4:34:41 PM 2 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR warning No index entry found for APPLICATIONS:\Microsoft Exchange 2010\.
63784 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. No previous replica date found to check for JET errors.
63786 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM set to check for all JET errors on replica.
63787 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. checkFor1018Errors = 1, checkFor1019Errors = 1, checkFor1022Errors = 1.
63788 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. execution of Exchange verification utility will be run with following params.
63790 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. execution of Exchange verification utility will go to vspwsbpdr01mp.
63792 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. execution of Exchange verification utility alt mountpath given C:\mnt.
70527 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. setting VSS backup level in RM struct to 1 -- Full .
79707 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. -A NSR_EXCH_CHECK value is passed in as no and the database EX3-DB2 is replicated, database consistency check will be skipped.
80245 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. checkFor447Errors = 1, checkFor448Errors = 1, DAG Name [SBP-DAG01].
69892 5/26/2016 4:34:41 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. singleThreadEseUtil = 1, throttleEseutil = 1, throttleIos = 100, throttleDuration = 1000
63773 5/26/2016 4:34:42 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. Writer Microsoft Exchange Replica Writer comp File was not explicitly added to backup\n.
63773 5/26/2016 4:34:42 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. Writer Microsoft Exchange Replica Writer comp Logs was not explicitly added to backup\n.
80823 5/26/2016 4:34:42 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. Exchange 2010 saveset Microsoft Exchange 2010 -- backup type PASSIVE added to the backup.
63352 5/26/2016 4:34:42 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. start the creation of a replica. Replica will be of type Default - which is VSS determined Non Transportable.
63586 5/26/2016 4:36:21 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. volume E:\ added to replica list.
63586 5/26/2016 4:36:21 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. volume F:\ added to replica list.
63586 5/26/2016 4:36:21 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. volume G:\ added to replica list.
63586 5/26/2016 4:36:21 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. volume I:\ added to replica list.
63354 5/26/2016 4:36:21 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. creation of replica succeeded.
83124 5/26/2016 4:36:22 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM disabling the Automount feature in order to do PS module proceed the import
64342 5/26/2016 4:36:23 PM 0 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR info NMM .. created XML file directory C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT26163623492.xml.
48574 5/26/2016 4:36:51 PM 5 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR critical PS: (CPSImportService::GetOperationStatus) ERR: Error for operation 1
63890 5/26/2016 4:36:51 PM 5 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR critical NMM .. Error encountered performing snapshot import: PS .. Error completing snapshot import
64034 5/26/2016 4:36:51 PM 5 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR critical NMM .. Error during import of snapshot: PS .. Error completing snapshot import.
63372 5/26/2016 4:36:51 PM 5 0 0 17924 17032 0 vspwsbpdr01mp nsrsnap_vss_save NSR critical NMM .. Registration of snapshot set failed -- PS .. Error completing snapshot import
0 events found


gautamgp
226 Posts
0
May 30th, 2016 01:00
Hi Murugan,
Check the windows eventviewer for VSS failure events. Check if the DB's are failing to perform the consistency check ?
MuruganMoorthy
22 Posts
0
May 31st, 2016 11:00
Hi Prakash,
We verified but we are getting same error only. While executing backup "Microsoft Exchange Replica Writer" going failed with Retry-able error. We restarted server and tried again its getting failed with same error.
Nitesh_Turkar
32 Posts
0
June 7th, 2016 02:00
Try to check basic things Like.
Communication between Physical nodes and DB health check.
Also share the application information that you have for all associated clients.
reytl
1 Message
0
May 5th, 2017 11:00
it was the error fixed? I'm having the same error for a SQL backup