Problem understanding the process to backup the MABS in event of DR condition

Lab Coat1 6 Reputation points
2023-02-03T19:00:07.1333333+00:00 
Looking for a way to recover a MABS server and/or database from failure so that I do not loose access to backups and the capability of restoring.

Is the following correct?
1. In main Azure Backup Server (one that is backing up VMs), create a protection group where the "local" Sql Database if protected.  To the same vault.
2. If the main ABS server and/or database becomes useless.  Then build a new one, and restore the database to it. (how is unclear. The four steps on the referenced site are lacking in specifics)
3. At this point configure protections will continue, and VMs can be restored from new and previous backups.
 
Is it that simple? Or am I missing something?

Looked at "https://learn.microsoft.com/en-us/azure/backup/backup-the-mabs-server"
Is there a better site to go to? Seems like there are missing parts to both backup and recovery.
It also does not generate confidence in this page that the link "List of Build Numbers for 
MABS" takes me to a page that was last updated in 2018

Referencing the site:
In "Back up the MABS database"
	Before you start, you'll need to run a script...
	A. Running the SQL script returns nothing.  Not even after "protecting" the DB.
	(is this a chicken/egg thing. Before you start, find the location of the backup. Which is not there before you do a backup first?)
	B. Then create a backup vault and install the agent????
	The MABS server is already installed and backing up VmWare hosts, both to disk and an Azure vault.
Is this referring to a secondary MABS server?



Have seen a lot of MS docs without a lot of detail or specific instructions.  More of an overview or checklist approach without defining what it means.
Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,133 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Prrudram-MSFT 22,396 Reputation points
    2023-03-04T18:26:59.4566667+00:00

    Hello @Lab Coat1

    Let me know if you wish to contact me offline we can discuss your queries better. If that is something you would like, you can send an email with the link to this thread to AzCommunity@microsoft.com with subject line as "ATTN: Priyanka"

    Let me give a little bit clarity in the meanwhile,
    Your understanding is correct in the first three points you have mentioned and I agree that the document is vast due to various methods of backing up the MABS database that has been documented. As a microsoft employee, I can take this feedback to the product documentation team to improve the document clarity.

    As part of your MABS backup strategy, you'll have to back up the MABS database. The MABS database is named DPMDB. This database contains the MABS configuration together with meta data about backups of MABS. If there's a disaster, you can rebuild most of the functionality of a MABS server by using a recent backup of the database.

    There are four database backup methods:

    Back up to Azure

    Back up the database by backing up the MABS storage pool

    Back up with native SQL Server backup to a local disk

    Back up with native SQL backup and MABS protection to a share protected by MABS

    Adding some imp points inline..

    1. In the main Azure Backup Server (one that is backing up VMs), create a protection group where the "local" Sql Database is protected to the same vault.
      If you back up by using a MABS protection group, we recommend that you use a unique protection group for the database.
    2. If the main ABS server and/or database becomes useless. Then build a new one and restore the database to it. (How is unclear. The four steps on the referenced site are lacking in specifics)
      I will add the exact steps below for your reference.
    3. At this point configure protections will continue, and VMs can be restored from new and previous backups.

    ***For restore purposes, the MABS installation you want to restore with the MABS database must match the version of the MABS database itself. For example, if the database you want to recover is from a MABS V3 with Update Rollup 1 installation, the MABS server must be running the same version with Update Rollup 1.

    How to Backup/Restore MABS DB to Azure (Method1)**

    The steps to recover a MABS server and/or database from failure are as follows:

    1. Create an Azure Backup vault, download the Azure Backup Agent installation file, and vault credentials.
    2. Run the installation file to install the agent **(MARS)**on the MABS server and use the vault credentials to register the MABS server in the vault. (Save the encryption passphrase somewhere safe)
    3. Set up a MABS protection group that contains the MABS database. Select to back it up to disk and to Azure.
    4. To recover the database from Azure, you can use any MABS server that's registered in the Azure Backup vault.
    5. In the MABS console, select Recovery > Add External MABS.
    6. Provide the vault credentials and select the MABS server for which you want to recover the database and click OK.
    7. Select the recovery point you want to use from the list of available points.

    Note: The agent that helps in backing up Azure backup server is called MARS.

    If this does answer your queries, please accept it as the answer as a token of appreciation.

    0 comments