Merge pull request #77829 from asgang/master

application consistent

Author: ktoliver

articles/site-recovery/azure-to-azure-troubleshoot-replication.md

@@ -74,11 +74,57 @@ For Site Recovery replication to work, outbound connectivity to specific URLs or
 
 ## Error ID 153006 - No app-consistent recovery point available for the VM in the last 'XXX' minutes
 
-To generate application consistent recovery points, Azure site recovery use VSS framework on Windows. </br>
 Some of the most common issues are listed below
 
-**Cause 1: Known issue on SQL server 2008/ 2008R2** </br>
-*How to fix* : There is a known issue with SQL server 2008/2008R2. Please refer this KB article [ASR Agent or other non-component VSS backup fails for a server hosting SQL Server 2008 R2](https://support.microsoft.com/help/4504103/non-component-vss-backup-fails-for-server-hosting-sql-server-2008-r2)
+#### Cause 1: Known issue on SQL server 2008/2008 R2 
+**How to fix** : There is a known issue with SQL server 2008/2008 R2. Please refer this KB article [Azure Site Recovery Agent or other non-component VSS backup fails for a server hosting SQL Server 2008 R2](https://support.microsoft.com/help/4504103/non-component-vss-backup-fails-for-server-hosting-sql-server-2008-r2)
 
-**Cause 2:** Azure Site Recovery jobs fail on servers hosting **any version** of SQL Server instances with AUTO_CLOSE DBs </br>
-*How to fix* : Refer Kb [article](https://support.microsoft.com/help/4504104/non-component-vss-backups-such-as-azure-site-recovery-jobs-fail-on-ser) 
+#### Cause 2: Azure Site Recovery jobs fail on servers hosting any version of SQL Server instances with AUTO_CLOSE DBs 
+**How to fix** : Refer Kb [article](https://support.microsoft.com/help/4504104/non-component-vss-backups-such-as-azure-site-recovery-jobs-fail-on-ser) 
+
+#### Cause 3: You are using Storage spaces direct configuration
+**How to fix** : Azure Site Recovery cannot create application consistent recovery point for Storage spaces direct configuration. Please refer article to correctly [configure the replication policy](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-how-to-enable-replication-s2d-vms)
+
+### More causes due to VSS related issues:
+
+To troubleshoot further, Check the files on the source machine to get the exact error code for failure:
+	
+	C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\Application Data\ApplicationPolicyLogs\vacp.log
+
+How to locate the errors in the file?
+Search for the string "vacpError"  by opening the vacp.log file in an editor
+		
+	Ex: vacpError:220#Following disks are in FilteringStopped state [\\.\PHYSICALDRIVE1=5, ]#220|^|224#FAILED: CheckWriterStatus().#2147754994|^|226#FAILED to revoke tags.FAILED: CheckWriterStatus().#2147754994|^|
+
+In the above example **2147754994** is the error code that tells you about the failure as shown below
+
+#### VSS writer is not installed - Error 2147221164 
+
+*How to fix*: To generate application consistency tag, Azure Site Recovery uses Microsoft Volume Shadow copy Service (VSS). It installs a VSS Provider for its operation to take app consistency snapshots. This VSS Provider is installed as a service. In case the VSS Provider service is not installed, the application consistency snapshot creation fails with the error id 0x80040154  "Class not registered". </br>
+Refer [article for VSS writer installation troubleshooting](https://docs.microsoft.com/azure/site-recovery/vmware-azure-troubleshoot-push-install#vss-installation-failures) 
+
+#### VSS writer is disabled - Error 2147943458
+
+**How to fix**: To generate application consistency tag, Azure Site Recovery uses Microsoft Volume Shadow copy Service (VSS). It installs a VSS Provider for its operation to take app consistency snapshots. This VSS Provider is installed as a service. In case the VSS Provider service is disabled, the application consistency snapshot creation fails with the error id "The specified service is disabled and cannot be started(0x80070422)". </br>
+
+- If VSS is disabled,
+    - Verify that the startup type of the VSS Provider service is set to **Automatic**.
+    - Restart the following services:
+        - VSS service
+        - Azure Site Recovery VSS Provider
+        - VDS service
+
+####  VSS PROVIDER NOT_REGISTERED - Error 2147754756
+
+**How to fix**: To generate application consistency tag, Azure Site Recovery uses Microsoft Volume Shadow copy Service (VSS). 
+Check if the Azure Site Recovery  VSS Provider service is installed or not. </br>
+
+- Retry the Provider installation using the following commands:
+- Uninstall existing provider: C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Uninstall.cmd
+- Reinstall: C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd
+ 
+Verify that the startup type of the VSS Provider service is set to **Automatic**.
+    - Restart the following services:
+        - VSS service
+        - Azure Site Recovery VSS Provider
+        - VDS service