Restoring Configuration Settings of Catalogic vStor

A vStor server’s configuration is crucial for recovery from failures like a corrupt machine. Even if the storage pool's disks are healthy, you might need to deploy a new vStor server and restore its configuration.

When to consider restoring?

After a Catastrophic Failure: If the vStor server fails but the SAN works, set up a new server and load the saved configuration during the first login.
When Moving to New Hardware: If you're shifting to better hardware, install vStor on it, reattach the pool disks, and load the saved configuration during the first login.

Restoring the Catalogic vStor configuration

Prerequisites

Remember that any changes made after the last backup and before a failure might be lost.

Before you restore, ensure the data on the pool disks is in a good state.

Attention! The archived database might be out of sync with recent changes. Data added after the last configuration backup won't be in the restored database. For example, if a backup is done at night and a crash occurs in the morning, new snapshots added after the backup won't be included.

Restoring configuration

During vStor Initialization:

Access and Login:
- Use a web browser to go to https://<vStor hostname or IP>:8900.
- Log in as admin.
Initiate Recovery:
- Choose Attempt config recovery at the prompt.
- Select the appropriate backup file, named pool-<#>-vstor_config_<date_and_time>.tar.gz.
Complete the Restoration:
- Click Load Configuration.
- The process could take up to 30 minutes. The system will update the database and notify partners.
- You will be logged out once completed. Log in again afterward.

Using vStor Web Interface After Initialization:

Navigate to System Config Recovery in the System Information pane
Confirm your backup choice.

Using vStor CLI:

Log In via SSH or Console:
- Log in as admin.
Run the Load Command:
- Ensure you select the correct backup file.
- Run: vstor system loadconfig --path /opt/vstor/backup/vstor_config_<date_and_time>.tar.gz.
Wait for Completion:
- The process takes up to 30 minutes.
- The database and SSH key are updated.
- You'll be logged out after the import.

Note. After loading a new database, you will need to log in again, because the new database is overwritten by the database copy from the archive, invalidating your current session.

PreviousBacking up Configuration Settings of Catalogic vStor NextAdding Disks

Last updated 5 months ago

When to consider restoring?

After a Catastrophic Failure: If the vStor server fails but the SAN works, set up a new server and load the saved configuration during the first login.

When Moving to New Hardware: If you're shifting to better hardware, install vStor on it, reattach the pool disks, and load the saved configuration during the first login.

Restoring the Catalogic vStor configuration

Prerequisites

Remember that any changes made after the last backup and before a failure might be lost.

Before you restore, ensure the data on the pool disks is in a good state.

Restoring configuration

During vStor Initialization:

Access and Login:

Use a web browser to go to https://<vStor hostname or IP>:8900.
Log in as admin.

Initiate Recovery:

Choose Attempt config recovery at the prompt.
Select the appropriate backup file, named pool-<#>-vstor_config_<date_and_time>.tar.gz.

Complete the Restoration:

Click Load Configuration.
The process could take up to 30 minutes. The system will update the database and notify partners.
You will be logged out once completed. Log in again afterward.

Using vStor Web Interface After Initialization:

Navigate to System Config Recovery in the System Information pane

Confirm your backup choice.

Using vStor CLI:

Log In via SSH or Console:

Run the Load Command:

Ensure you select the correct backup file.
Run: vstor system loadconfig --path /opt/vstor/backup/vstor_config_<date_and_time>.tar.gz.

Wait for Completion:

The process takes up to 30 minutes.
The database and SSH key are updated.
You'll be logged out after the import.

Note. After loading a new database, you will need to log in again, because the new database is overwritten by the database copy from the archive, invalidating your current session.