Disaster Recovery Strategy for MongoDB and VictoriaDB

Prerequisites

• A minimum of three nodes to enable High Availability are required

• MongoDB Version 6 is required for this setup

Steps to Deploy Pulse on New Node

1. Set the MongoDB URI:

2. Enable MongoDB Encryption:

3. Configure Pulse as a Standalone Node:

4. Create necessary directory structure:

5. Move the Pulse executable to the designated directory:

6. Navigate to the Pulse directory:

7. Initialize Pulse:

8. Source the environment variables:

9. Reinitialize Pulse:

10. Retrieve Pulse information:

11. Log in to Pulse Docker:

Add Host Entries

Add the following entries to the /etc/hosts file of all the MongoDB nodes, including the Pulse server:

Set New MongoDB Nodes

1. Retrieve the accelo binary and initiate it with the same version tag as the Pulse version on the primary node.

2. Login to the Pulse Registry:

3. Create a new Docker network:

4. Manually download the Mongo image:

Configuring the Primary Node (Pulse Server)

1. Edit Configuration File: In the config/docker/ad-core.yaml file, add the following new fields to the ad-db service section:

• Add the following fields to the environment block:

• Add the following fields to the volumes block:

• Add the following fields to the extra_hosts block:

2. Run Secondary Data Replica: Replace <Pulse-Server-IP>, <Third-Node-IP>, and <PULSE-VERSION> with the appropriate values and execute:

3. Run Third Data Replica: Replace <Pulse-Server-IP>, <Second-Node-IP>, and <PULSE-VERSION> with the appropriate values and execute:

4. Login to Primary Node's MongoDB Shell & Add Replica Members:

5. Check Replica Status: Run rs.status() to check the status of the replica.

6. Wait for Stable State: Wait for the MongoDB cluster to stabilize.

7. Update Mongodb Encrypted URI: Replace the MongoDB encrypted URI in all YAML files under config/docker/ and acceldata_acceluster.conf file with the provided value.

Unencrypted string for reference:

VictoriaDB Setup for Backup and Restoration

To setup Victoria database for backup and restore, perform the following:

1. Navigate to the Acceldata directory.

2. Fetch the binaries you want to backup and restore using the below command:

3. Extract the contents of the above tar file:

4. Remove unnecessary binaries, except vmbackup and vmrestore.

5. Execute the shell script:

6. Create a new directory for vmdbbackup as below:

7. Open up access to the ad-vmstorage port by modifying the ad-core.yml file as shown below.

8. Restart vmstorage container using:

9. Execute the following command. This command initiates an incremental backup process. Incremental backups are conducted when the destination (-dst) parameter refers to an existing backup directory. After the initial backup is completed, subsequent backups will always target this existing backup directory.

10. Configure the crontab to execute this task once daily, preferably in the morning:

Steps to Restore

To restore from backup, perform the following:

1. Stop the vmstorage container, if it already running, and run the restore command:

2. Run accelo deploy core

3. Check the logs of the container using docker logs -f ad-vmstorage_default

Troubleshooting

• If the backup process is slow, consider adjusting the value of the -concurrency flag to a higher setting. This will boost the number of simultaneous workers responsible for uploading data to the backup storage.

• If vmrestore or vmbackup encounters an interruption due to a temporary error, simply restart it using the same arguments. The process will resume from where it left off, continuing the restore or backup operation.