{"id":3739,"date":"2018-11-07T05:26:14","date_gmt":"2018-11-07T05:26:14","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=3739"},"modified":"2018-11-07T05:26:14","modified_gmt":"2018-11-07T05:26:14","slug":"cannot-stop-vpg-in-zerto-forcibly-delete-vpg-in-error-state-undo-log-isnt-empty-cant-start-new-transaction","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/cannot-stop-vpg-in-zerto-forcibly-delete-vpg-in-error-state-undo-log-isnt-empty-cant-start-new-transaction","title":{"rendered":"Cannot Stop VPG in Zerto – Forcibly delete VPG in Error State : Undo Log Isn’t Empty can’t start new transaction"},"content":{"rendered":"

Recently I tried to stop a VPG in Zerto after some DR testing, however, the Stop failed and the errors showing where :\u00a0<\/p>

Forcibly delete VPG in Error <\/strong>State : Undo Log Isn’t Empty can’t start <\/strong>new transaction<\/strong><\/p>

After lodging a call with Zerto Support, we had to forcibly remove the VPG Via Powershell and Re-Add it back<\/p>

**Before you do this I recommend you log down all the VM’s in the VPG and the Temp Data Drives<\/em><\/p>

You will need to download and install the Zerto Powershell Tools : Zerto.PS.Commands.Installer for your version<\/p>

After this is run you need to Open the Zerto Powershell and run\u00a0<\/p>

ForceRemove-ProtectionGroup<\/pre>
Enter the VPG Name without Quotes<\/p>
Enter the IP of the Zerto Server and username and password ( admin \/ password )\u00a0<\/p>
Once removed you can use the Zerto Virtual Replication Diagnostic Tool to import the VPG from the old setting file :<\/p>
\"\"<\/p>
Then navigate to :\u00a0<\/p>
C:\\Program Files\\Zerto\\Zerto Virtual Replication\\ExportedSettings<\/p>
Find the latest backup and try and re-import the VPG<\/p>
If this fails for whatever reason you will need to use the GUI at the customer side to recreate manually hence Note to backup VM names and Temp Data Drivers<\/p>","protected":false},"excerpt":{"rendered":"
Recently I tried to stop a VPG in Zerto after some DR testing, however, the Stop failed and the errors showing where :\u00a0Forcibly delete VPG in Error […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[2717,1344,2714,2715,2716,2449],"class_list":["post-3739","post","type-post","status-publish","format-standard","hentry","category-research","tag-cannot-stop","tag-error","tag-forceremove-protectiongroup","tag-vpg","tag-wont-stop","tag-zerto"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t