Backing up Configuration Settings of Catalogic vStor
Backing up the Catalogic vStor configuration is crucial for server recovery after a failure. The configuration, which includes the current state of volumes and snapshots, database configuration, replication shares, scheduled replications, SSH information, etc, is automatically backed up every 24 hours and stored on a designated configbackup volume. This volume can also be replicated to a partner vStor server. Additionally, a local copy is saved at:
A vStor server’s configuration is backed up automatically every 24 hours. That backup is retained for 14 days. This retention period may be modified in the system preferences by going to System > Preferences > clicking Edit and entering a new value for configBackupRetentionDays.Note.
Backing up the Catalogic vStor configuration
The latest backup determines the accuracy of your vStor server's state. If you don't backup after making changes, those changes might be lost if the server fails or gets corrupted.
Prerequisites
Create and Initialize a Pool: Make sure you have a pool set up.
Establish a Partnership: Have at least one partnership with another Catalogic vStor server.
Running backup manually
Log In to the vStor Server:
Use SSH or the console.
Log in as
admin.
Run the Backup Command:
Use command:
vstor system saveconfigA file will be saved in
/opt/vstor/backup.Filename format:
vstor_config_<date_and_time>.tar.gz.
Backup Volume Details:
In vStor UI, you'll see a
configbackupvolume for each pool, namedconfig_volume_pool_<#>-<vstor_system_id>.<#>= pool number,<vstor_system_id>= system ID of your vStor server.When replicated to a partner server, it appears as a filesystem type volume.
Optional - Mounting for Tape Backup:
The configuration volume can also be mounted via NFS for tape backup.
Last updated
Was this helpful?