Catalogic vStor Backup and Recovery

Warning! If you encounter errors during updates or backups in vStor 4.11, try the following:

1. Clean your user’s home directory (especially /home/admin) of unnecessary files.

2. Remove old backups from /opt/vstor/backup.

These steps may resolve operation timeout issues specific to vStor 4.11. This issue only concerns vStor 4.11.0 and has been fixed in vStor 4.11.1.

You can use Catalogic vStor for Block Backup and Agentless Backup. To use Catalogic vStor for File Backup and Image Backup, you have to create a disk directory on the Catalogic vStor server.

You can schedule and run backups and restores as usual, choosing the Catalogic vStor volume as the destination, as described in Block Backup in the DPX 4.12 Guide. For the backup destination, specify the Catalogic vStor volume.

Using Catalogic DPX Archive for Catalogic vStor Block Backups

The Catalogic DPX Archive is supported with the Catalogic vStor Block Backups.

Prerequisites:

1. Ensure Catalogic DPX Client is set up as a TCP/IP node on the vStor server.

2. The DPX client and vStor server must have matching resolvable node names (hostname or IP address).

3. Use the Block Backup Wizard or Archive to Media Wizard to schedule and run DPX Archive jobs as usual.

See also. Catalogic vStor can also work with the NetApp storage system. For details, see the DPX 4.12 Guide.

Using multipath storage for Catalogic vStor

To use multipath storage, including iSCSI and enterprise Fibre Channel with Catalogic vStor, you must enable the multipath access daemon (multipathd) and configure it properly.

Attention! The multipathd daemon must be configured and enabled on the Catalogic vStor server. Proper configuration is crucial to prevent issues like a disk being reported under multiple labels (e.g., /dev/sda and /dev/sdb).

Enabling the multipathd daemon in Catalogic vStor

Follow these steps to enable the multipathd daemon in the Catalogic vStor server with multipath storage:

1. Log in to the Catalogic vStor server using an SSH client and the dpxadmin account.

2. Create a multipath configuration file by executing: sudo mpathconf --enable.

3. Start and enable the multipathd daemon: sudo systemctl enable --now multipathd.

4. Verify that the service is running: systemctl status multipathd.

5. The daemon creates new devices in /dev/mapper (named mpath<x>), viewable with: sudo multipath -ll.

6. Use these mpath names in /dev/mapper for creating volumes, partitions, or file systems.

See also. For more details on best practices for backup storage, see Data Backup: Best Practices.