Skip to content

Commit 0fb6af0

Browse files
ShannonLeavittShannonLeavitt
authored
Merge pull request #82175 from ThalathBhagya/master
added cache folder content
2 parents ae0a4ef + 8f288d5 commit 0fb6af0

File tree

3 files changed

+97
-8
lines changed

3 files changed

+97
-8
lines changed

‎articles/backup/backup-azure-delete-vault.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,16 @@ If you delete a vault that contains dependencies, then it will display the follo
2323

2424
![delete vault error](./media/backup-azure-delete-vault/error.png)
2525

26-
To gracefully delete a vault follow the steps mentioned in the sequence below:
27-
- Stop protection and delete backup data
28-
- Delete the protected servers or backup management servers
29-
- Delete the vault
30-
26+
To gracefully delete the vault, choose the scenario that matches your setup and follow the recommended steps:
27+
28+
Scenario | Steps to remove dependencies to delete vault |
29+
-- | --
30+
I have on-premises Files and Folders protected using Azure Backup Agent (MARS) backing up to Azure | Perform the steps in Delete backup data and backup items - [For MARS agent](#for-mars-agent)
31+
I have on-premises machines protected using MABS (Microsoft Azure Backup Server) or DPM to Azure (System Center Data Protection Manager) | Perform the steps in Delete backup data and backup items - [For MABS agent](#for-mabs-agent)
32+
I have protected items in cloud (ex. laaS VM, Azure File Share etc.) | Perform the steps in Delete backup data and backup items - [For Protected items in Cloud](#for-protected-items-in-cloud)
33+
I have protected items both on-premises and cloud | Perform the steps in Delete backup data and backup items in the below sequence: <br> - [For Protected items in Cloud](#for-protected-items-in-cloud)<br> - [For MABS agent](#for-mars-agent) <br> - [For MABS agent](#for-mabs-agent)
34+
I don't have any protected items on-premises or cloud; however, I am still getting the Vault deletion error | Perform the steps in [Delete the Recovery Services vault using Azure Resource Manager client](#delete-the-recovery-services-vault-using-azure-resource-manager-client)
35+
I don't have that original on-premises server anymore (lost/decommissioned) and I want to delete the Recovery Services vault | Contact Microsoft support.
3136

3237
## Delete backup data and backup items
3338

‎articles/backup/backup-azure-mabs-troubleshoot.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,3 +114,33 @@ We recommend you perform the below validation, before you start troubleshooting
114114
| Operation | Error details | Workaround |
115115
| --- | --- | --- |
116116
| Setting up email notifications using an Office 365 account |Error ID: 2013| **Cause:**<br> Trying to use Office 365 account <br>**Recommended action:**<ol><li> The first thing to ensure is that “Allow Anonymous Relay on a Receive Connector” for your DPM server is set up on Exchange. For more information about how to configure this, see [Allow Anonymous Relay on a Receive Connector](https://technet.microsoft.com/library/bb232021.aspx) on TechNet.</li> <li> If you can't use an internal SMTP relay and need to set up by using your Office 365 server, you can set up IIS to be a relay. Configure the DPM server to [relay the SMTP to O365 using IIS](https://technet.microsoft.com/library/aa995718(v=exchg.65).aspx).<br><br> **IMPORTANT:** Be sure to use the user\@domain.com format and *not* domain\user.<br><br><li>Point DPM to use the local server name as SMTP server, port 587. Then point it to the user email that the emails should come from.<li> The username and password on the DPM SMTP setup page should be for a domain account in the domain that DPM is on. </li><br> **NOTE**: When you are changing the SMTP server address, make the change to the new settings, close the settings box, and then reopen it to be sure it reflects the new value. Simply changing and testing might not always cause the new settings to take effect, so testing it this way is a best practice.<br><br>At any time during this process, you can clear these settings by closing the DPM console and editing the following registry keys: **HKLM\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Notification\ <br/> Delete SMTPPassword and SMTPUserName keys**. You can add them back to the UI when you launch it again.
117+
118+
119+
## Common issues
120+
121+
This section covers the common errors that you might encounter while using Azure Backup Server.
122+
123+
124+
### CBPSourceSnapshotFailedReplicaMissingOrInvalid
125+
126+
Error message | Recommended action |
127+
-- | --
128+
Backup failed because the disk-backup replica is either invalid or missing. | To resolve this issue, verify the below steps and retry the operation: <br/> 1. Create a disk recovery point<br/> 2. Run consistency check on datasource <br/> 3. Stop protection of datasource and then reconfigure protection for this data source
129+
130+
### CBPSourceSnapshotFailedReplicaMetadataInvalid
131+
132+
Error message | Recommended action |
133+
-- | --
134+
Source volume snapshot failed because metadata on replica is invalid. | Create a disk recovery point of this datasource and retry online backup again
135+
136+
### CBPSourceSnapshotFailedReplicaInconsistent
137+
138+
Error message | Recommended action |
139+
-- | --
140+
Source volume snapshot failed due to inconsistent datasource replica. | Run a consistency check on this datasource and try again
141+
142+
### CBPSourceSnapshotFailedReplicaCloningIssue
143+
144+
Error message | Recommended action |
145+
-- | --
146+
Backup failed as the disk-backup replica could not be cloned.| Ensure that all previous disk-backup replica files (.vhdx) are unmounted and no disk to disk backup is in progress during online backups

‎articles/backup/backup-azure-mars-troubleshoot.md

Lines changed: 57 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: saurabhsensharma
66
manager: sivan
77
ms.service: backup
88
ms.topic: conceptual
9-
ms.date: 07/05/2019
9+
ms.date: 07/15/2019
1010
ms.author: saurse
1111
---
1212

@@ -160,8 +160,62 @@ Azure Backup might not successfully mount the recovery volume, even after severa
160160

161161
If the recovery still fails, restart your server or client. If you don't want to restart, or if the recovery still fails even after you restart the server, try [recovering from another machine](backup-azure-restore-windows-server.md#use-instant-restore-to-restore-data-to-an-alternate-machine).
162162

163-
## Need help? Contact support
164-
If you still need help, [contact support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade) to get your problem resolved quickly.
163+
164+
## Troubleshoot Cache problems
165+
166+
Backup operation may fail if the cache folder (also referred as scratch folder) is incorrectly configured, missing pre-requisites or has restricted access.
167+
168+
### Pre-requisites
169+
170+
For MARS agent operations to succeed the cache folder needs to adhere to the below requirements:
171+
172+
- [Ensure 5% to 10% free volume space is available in the scratch folder location](backup-azure-file-folder-backup-faq.md#whats-the-minimum-size-requirement-for-the-cache-folder)
173+
- [Ensure scratch folder location is valid and accessible](backup-azure-file-folder-backup-faq.md#how-to-check-if-scratch-folder-is-valid-and-accessible)
174+
- [Ensure file attributes on the cache folder are supported](backup-azure-file-folder-backup-faq.md#are-there-any-attributes-of-the-cache-folder-that-arent-supported)
175+
- [Ensure the allocated shadow copy storage space is sufficient for backup process](#increase-shadow-copy-storage)
176+
- [Ensure there are no other processes (ex. anti-virus software) restricting access to cache folder](#another-process-or-antivirus-software-blocking-access-to-cache-folder)
177+
178+
### Increase shadow copy storage
179+
Backup operations could fail if there is insufficient shadow copy storage space required to protect the data source. To resolve this issue increase the shadow copy storage space on the protected volume using vssadmin as shown below:
180+
- Check the current shadow storage space from the elevated command prompt:<br/>
181+
`vssadmin List ShadowStorage /For=[Volume letter]:`
182+
- Increase the shadow storage space using the below command:<br/>
183+
`vssadmin Resize ShadowStorage /On=[Volume letter]: /For=[Volume letter]: /Maxsize=[size]`
184+
185+
### Another process or antivirus software blocking access to cache folder
186+
If you have antivirus software installed on the server, add necessary exclusion rules to the antivirus scan for these files and folders:
187+
- The scratch folder. Its default location is C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch
188+
- The bin folder at C:\Program Files\Microsoft Azure Recovery Services Agent\Bin
189+
- CBengine.exe
190+
- CSC.exe
191+
192+
## Common issues
193+
This section covers the common errors that you encounter while using MARS agent.
194+
195+
### SalChecksumStoreInitializationFailed
196+
197+
Error message | Recommended action |
198+
-- | --
199+
Microsoft Azure Recovery Services Agent was unable to access backup checksum stored in scratch location | To resolve this issue, perform the below and restart the server <br/> - [Check if there is an antivirus or other processes locking the scratch location files](#another-process-or-antivirus-software-blocking-access-to-cache-folder)<br/> - [Check if the scratch location is valid and accessible to mars agent.](backup-azure-file-folder-backup-faq.md#how-to-check-if-scratch-folder-is-valid-and-accessible)
200+
201+
### SalVhdInitializationError
202+
203+
Error message | Recommended action |
204+
-- | --
205+
Microsoft Azure Recovery Services Agent was unable to access the scratch location to initialize VHD | To resolve this issue, perform the below and restart the server <br/> - [Check if there is an antivirus or other processes locking the scratch location files](#another-process-or-antivirus-software-blocking-access-to-cache-folder)<br/> - [Check if the scratch location is valid and accessible to mars agent.](backup-azure-file-folder-backup-faq.md#how-to-check-if-scratch-folder-is-valid-and-accessible)
206+
207+
### SalLowDiskSpace
208+
209+
Error message | Recommended action |
210+
-- | --
211+
Backup failed due to insufficient storage in volume where the scratch folder is located | To resolve this issue, verify the below steps and retry the operation:<br/>- [Ensure MARS agent is latest](https://go.microsoft.com/fwlink/?linkid=229525&clcid=0x409)<br/> - [Verify and resolve storage issues that impact backup scratch space](#pre-requisites)
212+
213+
### SalBitmapError
214+
215+
Error message | Recommended action |
216+
-- | --
217+
Unable to find changes in a file. This could be due to various reasons. Please retry the operation | To resolve this issue, verify the below steps and retry the operation:<br/> - [Ensure MARS agent is latest](https://go.microsoft.com/fwlink/?linkid=229525&clcid=0x409) <br/> - [Verify and resolve storage issues that impact backup scratch space](#pre-requisites)
218+
165219

166220
## Next steps
167221
* Get more details on [how to back up Windows Server with the Azure Backup agent](tutorial-backup-windows-server-to-azure.md).

0 commit comments

Comments
 (0)