You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-afs-automation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -271,7 +271,7 @@ Azure file share snapshots are used while the backups are taken, so usually the
271
271
272
272
### Using on-demand backups to extend retention
273
273
274
-
On-demand backups can be used to retain your snapshots for 10 years. Schedulers can be used to run on-demand PowerShell scripts with chosen retention and thus take snapshots at regular intervals every week, month, or year. While taking regular snapshots refer to the [limitations of on-demand backups](https://docs.microsoft.com/azure/backup/backup-azure-files-faq#how-many-on-demand-backups-can-i-take-per-file-share-) using Azure backup.
274
+
On-demand backups can be used to retain your snapshots for 10 years. Schedulers can be used to run on-demand PowerShell scripts with chosen retention and thus take snapshots at regular intervals every week, month, or year. While taking regular snapshots, refer to the [limitations of on-demand backups](https://docs.microsoft.com/azure/backup/backup-azure-files-faq#how-many-on-demand-backups-can-i-take-per-file-share) using Azure backup.
275
275
276
276
If you are looking for sample scripts, you can refer to the sample script on GitHub (<https://github.com/Azure-Samples/Use-PowerShell-for-long-term-retention-of-Azure-Files-Backup)> using Azure Automation runbook that enables you to schedule backups on a periodic basis and retain them even up to 10 years.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-arm-userestapi-backupazurevms.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,7 @@ In the example, the above values translate to:
163
163
164
164
### Enabling protection for the Azure VM
165
165
166
-
After the relevant VM is "cached" and "identified", select the policy to protect. To know more about existing policies in the vault, refer to [list Policy API](https://docs.microsoft.com/rest/api/backup/backuppolicies/list). Then select the [relevant policy](https://docs.microsoft.com/rest/api/backup/protectionpolicies/get) by referring to the policy name. To create policies, refer to [create policy tutorial](backup-azure-arm-userestapi-createorupdatepolicy.md). "DefaultPolicy" is selected in the below example.
166
+
After the relevant VM is "cached" and "identified", select the policy to protect. To know more about existing policies in the vault, refer to [list Policy API](https://docs.microsoft.com/rest/api/backup/backuppolicies/list). Then select the [relevant policy](https://docs.microsoft.com/rest/api/backup/protectionpolicies(2019-05-13)/get) by referring to the policy name. To create policies, refer to [create policy tutorial](backup-azure-arm-userestapi-createorupdatepolicy.md). "DefaultPolicy" is selected in the below example.
167
167
168
168
Enabling protection is an asynchronous *PUT* operation that creates a 'protected item'.
6. In the **certs** folder, right-click the root certificate file > **Rename**.
67
66
@@ -77,7 +76,7 @@ Set up a secure channel as follows:
77
76
78
77
10. On the **Certificate Store** page, select **Place all certificates in the following store**, and then click **Browse** to choose the certificate store.
11. In **Select Certificate Store**, select **Trusted Root Certification Authorities** as the destination folder for the certificates, and then click **OK**.
83
82
@@ -95,11 +94,11 @@ If you have secure boundaries within your organization, and don't want to use th
95
94
96
95
1. Copy and paste the following text into a .txt file.
97
96
98
-
```text
97
+
```text
99
98
Windows Registry Editor Version 5.00
100
99
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\VMWare]
101
100
"IgnoreCertificateValidation"=dword:00000001
102
-
```
101
+
```
103
102
104
103
2. Save the file on the Azure Backup Server machine with the name **DisableSecureAuthentication.reg**.
105
104
@@ -125,7 +124,7 @@ The Azure Backup Server needs a user account with permissions to access v-Center
125
124
- To select the VirtualMachine privileges, you need to go several levels into the parent child hierarchy.
126
125
- You don't need to select all child privileges within a parent privilege.
2. In the **vCenter Users and Groups** panel, select the **Users** tab, and then click the add users icon (the + symbol).
162
161
163
-
162
+
164
163
165
164
3. In **New User** dialog box, add the user information > **OK**. In this procedure, the username is BackupAdmin.
166
165
@@ -216,7 +215,7 @@ Add the vCenter Server to Azure Backup Server.
216
215
217
216
2. In **Production Server Addition Wizard** > **Select Production Server type** page, select **VMware Servers**, and then click **Next**.
218
217
219
-
218
+
220
219
221
220
3. In **Select Computers****Server Name/IP Address**, specify the FQDN or IP address of the VMware server. If all the ESXi servers are managed by the same vCenter, specify the vCenter name. Otherwise, add the ESXi host.
222
221
@@ -261,7 +260,7 @@ Add VMware VMs for backup. Protection groups gather multiple VMs and apply the s
261
260
- When you select a folder, or VMs or folders inside that folder are also selected for backup. You can uncheck folders or VMs you don't want to back up.
262
261
1. If a VM or folder is already being backed up, you can't select it. This ensures that duplicate recovery points aren't created for a VM.
263
262
264
-
263
+
265
264
266
265
1. In **Select Data Protection Method** page, enter a name for the protection group, and protection settings. To back up to Azure, set short-term protection to **Disk** and enable online protection. Then click **Next**.
267
266
@@ -285,40 +284,40 @@ Add VMware VMs for backup. Protection groups gather multiple VMs and apply the s
285
284
-**Automatically grow:** If you turn on this setting, if data in the protected group outgrows the initial allocation, Azure Backup Server tries to increase the disk size by 25 percent.
286
285
-**Storage pool details:** Shows the status of the storage pool, including total and remaining disk size.
287
286
288
-
287
+
289
288
290
289
1. In **Choose Replica Creation Method** page, specify how you want to take the initial backup, and then click **Next**.
291
290
- The default is **Automatically over the network** and **Now**.
292
291
- If you use the default, we recommend that you specify an off-peak time. Choose **Later** and specify a day and time.
293
292
- For large amounts of data or less-than-optimal network conditions, consider replicating the data offline by using removable media.
1. In **Consistency Check Options**, select how and when to automate the consistency checks. Then click **Next**.
298
297
- You can run consistency checks when replica data becomes inconsistent, or on a set schedule.
299
298
- If you don't want to configure automatic consistency checks, you can run a manual check. To do this, right-click the protection group > **Perform Consistency Check**.
300
299
301
300
1. In **Specify Online Protection Data** page, select the VMs or VM folders that you want to back up. You can select the members individually, or click **Select All** to choose all members. Then click **Next**.
1. On the **Specify Online Retention Policy** page, indicate how long you want to keep the recovery points that are created from the daily/weekly/monthly/yearly backups to Azure. then click **Next**.
313
312
314
313
- There's no time limit for how long you can keep data in Azure.
315
314
- The only limit is that you can't have more than 9999 recovery points per protected instance. In this example, the protected instance is the VMware server.
11. In **Choose Initial Backup Type** decide if you want to take the initial backup over the network or use offline backup (for more information on offline backup refer, see this [article](backup-azure-backup-import-export.md)). To take the initial backup over the network, select **Automatically over the network** and click **Next**.
63
63
@@ -160,7 +160,7 @@ There are two ways to stop protecting Files and Folders backup:
160
160
161
161
1. In **Select Policy Item** page, select **Modify a backup schedule for your files and folders** click **Next**.
162
162
163
-
1. From the **Modify or Stop a Scheduled Backup** page, select **Stop using this backup schedule, but keep the stored backups till a schedule is activated again**. Then, select **Next**.
163
+
1. From the **Modify or Stop a Scheduled Backup** page, select **Stop using this backup schedule, but keep the stored backups until a schedule is activated again**. Then, select **Next**.
164
164
165
165
1. In **Pause Scheduled Backup** review the information click **Finish**
166
166
Copy file name to clipboardExpand all lines: articles/backup/restore-sql-database-azure-vm.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,9 +72,9 @@ Restore as follows:
72
72
-**Alternate Location**: Restore the database to an alternate location and keep the original source database.
73
73
-**Overwrite DB**: Restore the data to the same SQL Server instance as the original source. This option overwrites the original database.
74
74
75
-
> [!IMPORTANT]
76
-
> If the selected database belongs to an Always On availability group, SQL Server doesn't allow the database to be overwritten. Only **Alternate Location** is available.
77
-
>
75
+
> [!IMPORTANT]
76
+
> If the selected database belongs to an Always On availability group, SQL Server doesn't allow the database to be overwritten. Only **Alternate Location** is available.
77
+
>
78
78
-**Restore as files**: Instead of restoring as a database, restore the backup files that can be recovered as a database later on any machine where the files are present using SQL Server Management Studio.
0 commit comments