Merge pull request #89062 from ThalathBhagya/master

updated content

Author: ktoliver

articles/backup/backup-azure-files.md

@@ -82,14 +82,16 @@ Occasionally you may want to generate a backup snapshot, or recovery point, outs
 
    ![click Backup to associate the Azure file share with vault](./media/backup-file-shares/list-of-azure-files-backup-items.png)
 
-3. From the list of Azure file shares, select the desired file share. The Backup Item menu for the selected file share opens.
+3. From the list of Azure file shares, select the desired file share. The **Backup Item** details appears. From the **Backup Item** menu, click **Backup now**. Because this is an on-demand backup job, there is no retention policy associated with the recovery point.
 
    ![click Backup to associate the Azure file share with vault](./media/backup-file-shares/backup-item-menu.png)
 
-4. From the Backup Item menu, click **Backup Now**. Because this is an on-demand backup job, there is no retention policy associated with the recovery point. The **Backup Now** dialog opens. Specify the last day you want to retain the recovery point.
+4. The **Backup Now** dialog opens. Specify the last day you want to retain the recovery point.
 
    ![click Backup to associate the Azure file share with vault](./media/backup-file-shares/backup-now-menu.png)
 
+5. Click **Ok** to confirm the on-demand backup job.
+
 ## Restore from backup of Azure file share
 If you need to restore an entire file share or individual files or folders from a Restore Point, head to the Backup Item as detailed in the previous section. Choose **Restore Share** to restore an entire file share from a desired Point-in-time. From the list of Restore Points that show up, select one to be able to Overwrite your current file share or Restore this to an alternate file share in the same region.
 

articles/backup/backup-azure-manage-vms.md

@@ -159,6 +159,13 @@ There are two ways to delete a VM's backup data:
   > [!NOTE]
   > When you delete backup data you delete all associated recovery points. You can't choose specific recovery points to delete.
 
+### Backup item where primary data source no longer exists
+
+- If Azure VMs configured for Azure backup are either deleted or moved without stopping protection, then both scheduled backup jobs and on demand (ad-hoc) backup jobs will fail with the error UserErrorVmNotFoundV2. The backup pre-check will appear as critical only for failed ad-hoc backup jobs (failed scheduled jobs are not displayed). 
+- These backup items remain active in the system adhering to the backup and retention policy set by the user. The backed-up data for these Azure VMs will be retained according to the retention policy. The expired recovery points (except the last recovery point) are cleaned according to the retention range set in the backup policy.
+- Users are recommended to delete the backup items where the primary data source no longer exists to avoid any additional cost, if the backup item/data for the delete resources is no longer required as the last recovery point is retained forever and the user is charged as per the backup pricing applicable.
+
+
 ## Next steps
 - Learn how to [back up Azure VMs from the VM's settings](backup-azure-vms-first-look-arm.md).
 - Learn how to [restore VMs](backup-azure-arm-restore-vms.md).

articles/backup/backup-azure-security-feature-cloud.md

@@ -116,9 +116,9 @@ Undelete followed by resume operation will protect the resource again. Resume op
 
 Recovery Services vault cannot be deleted if there are backup items in soft-deleted state in the vault. The soft-deleted items are permanently deleted after 14 days of delete operation. You can delete the vault only after all the soft deleted items have been purged.  
 
-#### How can I delete the data earlier than the 14 days soft-delete period after deletion?
+#### Can I delete the data earlier than the 14 days soft-delete period after deletion?
 
-There is no way to purge the data before the 14 days after deletion. If it is a blocker or a compliance issue, please contact Microsoft support.
+No. You cannot force delete the soft-deleted items, they are automatically deleted after 14 days. This security feature is enabled to safeguard the backed-up data from accidental or malicious deletes.  You should wait for 14 day before performing any other action on the VM.  Soft-deleted items will not be charged.  If you need re-protecting the VMs marked for soft-delete within 14 days to a new vault then contact Microsoft support.
 
 #### Can soft delete operations be performed in PowerShell or CLI?
 

articles/backup/backup-azure-vms-troubleshoot.md

@@ -180,10 +180,10 @@ This will ensure the snapshots are taken through host instead of Guest. Retry th
 
 | Error details | Workaround |
 | ------ | --- |
-| **Error code**: 320001<br/> **Error message**: Could not perform the operation as VM no longer exists. <br/> <br/> **Error code**: 400094 <br/> **Error message**: The virtual machine doesn't exist <br/> <br/>  An Azure virtual machine wasn't found.  |This error happens when the primary VM is deleted, but the backup policy still looks for a VM to back up. To fix this error, take the following steps: <ol><li> Re-create the virtual machine with the same name and same resource group name, **cloud service name**,<br>**or**</li><li> Stop protecting the virtual machine with or without deleting the backup data. For more information, see [Stop protecting virtual machines](backup-azure-manage-vms.md#stop-protecting-a-vm).</li></ol>|
-| The VM is in failed provisioning state: <br>Restart the VM and make sure the VM is running or shut down. | This error occurs when one of the extension failures puts the VM into failed provisioning state. Go to the extensions list, check if there's a failed extension, remove it, and try restarting the virtual machine. If all extensions are in running state, check if the VM Agent service is running. If not, restart the VM Agent service. |
+| **Error code**: 320001, ResourceNotFound <br/> **Error message**: Could not perform the operation as VM no longer exists. <br/> <br/> **Error code**: 400094, BCMV2VMNotFound <br/> **Error message**: The virtual machine doesn't exist <br/> <br/>  An Azure virtual machine wasn't found.  |This error happens when the primary VM is deleted, but the backup policy still looks for a VM to back up. To fix this error, take the following steps: <ol><li> Re-create the virtual machine with the same name and same resource group name, **cloud service name**,<br>**or**</li><li> Stop protecting the virtual machine with or without deleting the backup data. For more information, see [Stop protecting virtual machines](backup-azure-manage-vms.md#stop-protecting-a-vm).</li></ol>|
+| **Error code**: UserErrorVmProvisioningStateFailed<br/> **Error message**: The VM is in failed provisioning state: <br>Restart the VM and make sure the VM is running or shut down. | This error occurs when one of the extension failures puts the VM into failed provisioning state. Go to the extensions list, check if there's a failed extension, remove it, and try restarting the virtual machine. If all extensions are in running state, check if the VM Agent service is running. If not, restart the VM Agent service. |
 |**Error code**: UserErrorBCMPremiumStorageQuotaError<br/> **Error message**: Could not copy the snapshot of the virtual machine, due to insufficient free space in the storage account | For premium VMs on VM backup stack V1, we copy the snapshot to the storage account. This step makes sure that backup management traffic, which works on the snapshot, doesn't limit the number of IOPS available to the application using premium disks. <br><br>We recommend that you allocate only 50 percent, 17.5 TB, of the total storage account space. Then the Azure Backup service can copy the snapshot to the storage account and transfer data from this copied location in the storage account to the vault. |
-| **Error code: 380008** <br/> **Error message**: Failed to install Microsoft Recovery Services extension as virtual machine is not running | The VM Agent is a prerequisite for the Azure Recovery Services extension. Install the Azure Virtual Machine Agent and restart the registration operation. <br> <ol> <li>Check if the VM Agent is installed correctly. <li>Make sure that the flag on the VM config is set correctly.</ol> Read more about installing the VM Agent and how to validate the VM Agent installation. |
+| **Error code**: 380008, AzureVmOffline <br/> **Error message**: Failed to install Microsoft Recovery Services extension as virtual machine  is not running | The VM Agent is a prerequisite for the Azure Recovery Services extension. Install the Azure Virtual Machine Agent and restart the registration operation. <br> <ol> <li>Check if the VM Agent is installed correctly. <li>Make sure that the flag on the VM config is set correctly.</ol> Read more about installing the VM Agent and how to validate the VM Agent installation. |
 | **Error code**: ExtensionSnapshotBitlockerError <br/> **Error message**: The snapshot operation failed with the Volume Shadow Copy Service (VSS) operation error **This drive is locked by BitLocker Drive Encryption. You must unlock this drive from the Control Panel.** |Turn off BitLocker for all drives on the VM and check if the VSS issue is resolved. |
 | **Error code**: VmNotInDesirableState <br/> **Error message**:  The VM isn't in a state that allows backups. |<ul><li>If the VM is in a transient state between **Running** and **Shut down**, wait for the state to change. Then trigger the backup job. <li> If the VM is a Linux VM and uses the Security-Enhanced Linux kernel module, exclude the Azure Linux Agent path **/var/lib/waagent** from the security policy and make sure the Backup extension is installed.  |
 | The VM Agent isn't present on the virtual machine: <br>Install any prerequisite and the VM Agent. Then restart the operation. |Read more about [VM Agent installation and how to validate VM Agent installation](#vm-agent). |