Skip to content

Commit 284ba02

Browse files
updates
1 parent 85e6dcf commit 284ba02

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/backup/backup-azure-microsoft-azure-backup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -307,8 +307,6 @@ Use the following procedures to upgrade MABS.
307307
308308
> MABS V2 is not a prerequisite for installing MABS V3. However, you can upgrade to MABS V3 only from MABS V2.
309309
310-
> when configuring SQL 2017 manually, refer to *SSRS configuration with SQL 2017* section under Install instructions
311-
312310
Use the following steps to upgrade MABS:
313311

314312
1. To upgrade from MABS V2 to MABS V3, upgrade your OS to Windows Server 2016 or Windows Server 2019 if needed.
@@ -325,6 +323,8 @@ Use the following steps to upgrade MABS:
325323
326324
> As part of SQL 2017 upgrade, we backup the SQL encryption keys and uninstall the reporting services. After SQL server upgrade, reporting service(14.0.6827.4788) is installed & encryption keys are restored.
327325
326+
> When configuring SQL 2017 manually, refer to *SSRS configuration with SQL 2017* section under Install instructions.
327+
328328
3. Update the protection agents on the protected servers.
329329
4. Backups should continue without the need to restart your production servers.
330330
5. You can begin protecting your data now. If you are upgrading to Modern Backup Storage, while protecting, you can also choose the volumes you wish to store the backups in, and check for under provisioned space. [Learn more](backup-mabs-add-storage.md).

0 commit comments

Comments
 (0)