Open topic with navigation

Disconnected: You’re looking at a local copy of the Appliance Controller Documentation Center. The most current version is online at www.quantum.com/accdocs.

# Backup and Restore

Use the `system backup` and `system restore` commands to protect the configuration information controlled by and stored in the Appliance Controller.

System Backup

Overview

When you begin to configure your Appliance Controller features, a small configuration file is placed in the root directory of the StorNext file system. The `system backup` command protects this configuration file.

If you have a managed file system, your configuration file is stored in the .ADIC_INTERNAL_BACKUP/snnas directory of your StorNext file system. Placing backup configuration files on a managed file system ensures that redundant copies of the configuration are protected.

By default, the `system backup` command automatically runs once a day. You can manually back up the Appliance Controller's configuration file at any time, and we recommend running a manual backup after the file has been modified.

Backing up your system

By default, the `system backup` command automatically runs once a day to protect your Appliance Controller's configuration file. You can manually back up the configuration file at any time, and we recommend running a manual backup after the file has been modified.

Before you begin
For releases prior to 2.3.0 – turn off the NO_STORE Flag to protect Appliance Controller configuration files on Xcellis Workflow Extender and G300 gateway systems

Note: This is required ONLY for Appliance Controller releases prior to 2.3.0.

Ensure that the .ADIC_INTERNAL_BACKUP/snnas directory has the NO_STORE flag turned off. Otherwise the Appliance Controller's configuration file will not be backed up.

1. Log in to the Appliance Controller CLI.
2. At the prompt, enter the following:

   /usr/adic/TSM/util/dm_util -d no_store <managed_file_system>/.ADIC_INTERNAL_BACKUP/snnas

   Important

   Always execute the `dm_util` command. Otherwise, the Appliance Controller's configuration file may not be copied to tiers managed by File Manager.

Backup ctdb configuration

In addition to running the `system backup`, Quantum recommends manually backing up ctdb configuration.

Note: The `system backup` command currently does not back up ctdb, which is required for normal Appliance Controller operations.

To backup ctdb configuration:

Open an SSH connection to the server and use the IP address used to access the server on the Management (public) or LAN Client (private) network:

1. Log in to the command line using the following credentials:
   - User name: stornext
   - Password: <StorNext user account password>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password. The first time you log in, you are prompted to change the password to a different one.

2. Enter `sudo rootsh` to gain root user access.
3. Enter the password for the `stornext` user account again.

Note: If the password for the `stornext` user account was changed after installation, use the current password.

1. Create a directory for ctdb:

   Example:

   > `mkdir /home/stornext/ctdb_bak`

2. Copy ctdb from the source directory to the backup directory:

   Example:

   > `cp /stornext/MEDIA_XSAN/.StorNext/.snnas/ctdb/* /home/stornext/ctdb_bak`

3. Run the `system backup`as described in the next section.

To restore ctdb configuration:

Caution: The following procedure will REPLACE the files in the ctdb directory. ONLY attempt this procedure if a `system restore` is run, and the ctdb configuration file is missing.

Open an SSH connection to the server and use the IP address used to access the server on the Management (public) or LAN Client (private) network:

1. Log in to the command line using the following credentials:
   - User name: stornext
   - Password: <StorNext user account password>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password. The first time you log in, you are prompted to change the password to a different one.

2. Enter `sudo rootsh` to gain root user access.
3. Enter the password for the `stornext` user account again.

Note: If the password for the `stornext` user account was changed after installation, use the current password.

1. Copy ctdb from the backup directory to the source directory:

   Example:

   > `cp /home/stornext/ctdb_bak/* /stornext/MEDIA_XSAN/.StorNext/.snnas/ctdb/`

2. Confirm replacement, if prompted.

The ctdb restore process is complete.

Perform a Manual System Backup

1. Log in to the Appliance Controller CLI.
2. At the prompt, enter the following:

   > `system backup`

   Example:

   > `system backup`

   Creating configuration backup /var/snnas-db-package.tar.bz2.enc (79 KB)

   Finished configuration backup /var/snnas-db-package.tar.bz2.enc (79 KB)

   Saved configuration backup package /var/snnas-db-package.tar.bz2.enc to /stornext/snfs1/.StorNext/.snnas/snnas-db-package.tar.bz2.enc.ceb028ca81a211e587c7ecf4bbdc1708

   Backup of configuration successful

   Example (Managed File System):

   > system backup

   Gathering configuration backup data

   Finished configuration backup /var/snnas-db-package.tar.bz2.enc (971 KB)

   Saved configuration backup package /var/snnas-db-package.tar.bz2.enc to /stornext/snfs1m/.ADIC_INTERNAL_BACKUP/snnas/snnas-db-package.tar.bz2.enc.a7251c34841311e5976d0050569b7d37

   Backup of configuration successful

System Restore

If you need to restore the Appliance Controller's configuration file from a previous backup, run the`system restore` command. The most recent backup file will be in the /var directory. If you do not want to restore from the most recent configuration file, make sure that the file from which to restore system configuration is in the /var directory.

To Restore Your System

Restore Nodes in a NAS Cluster

When you need to restore the Appliance Controller configuration in a clustered NAS environment, you will need to synchronize the sync data to all nodes in the NAS cluster, and then recreate the NAS cluster. However, you can only run the "system restore" command on the master node, and only if it's first removed from the NAS cluster before attempting using the system `restore command` on the master node.

1. Log in to the Appliance Controller CLI.
2. At the prompt, enter:

nascluster show

3. Record current NAS cluster settings.
4. Delete the NAS cluster. See Delete a NAS Cluster (return to non-clustered state).
5. Perform a "system restore" on the master node. At the prompt, enter:

system restore

Example

> system restore

Are you sure you want to restore the configuration from backup (Yes/no)? Yes

Restore of configuration in-progress ...

Restore of configuration successful

Restarting services ...

Stopping all services . . .

keepalived

haproxy

winbind

smbd

ctdb

console

appliance_controller

Starting all services . . .

appliance_controller

console

ctdb

smbd

winbind

haproxy

keepalived

6. Recreate the NAS cluster (using the settings recorded earlier in step 3). See Task 1: Create a NAS Cluster.

Perform a System Restore without NAS Clusters Enabled (single server node)

If you need to restore the Appliance Controller's configuration file from a previous backup, run the`system restore` command. The most recent configuration file will be in the /var directory. However, if you do not want to restore from the most recent configuration file, make sure that the file from which to restore system configuration is in the /var directory.

1. Log in to the Appliance Controller CLI.
2. At the prompt, enter:

`system restore`

Example

> system restore

Are you sure you want to restore the configuration from backup (Yes/no)? Yes

Restore of configuration in-progress ...

Restore of configuration successful

Restarting services ...

Stopping all services . . .

keepalived

haproxy

winbind

smbd

ctdb

console

appliance_controller

Starting all services . . .

appliance_controller

console

ctdb

smbd

winbind

haproxy

keepalived

6-68456-07_RevA | Initial publication date: Friday, December 22, 2017 | Last updated on Monday, January 12, 2026.

Open topic with navigation