Prior to running the backup or restore methods, the necessary permissions must
be setup for them to work.  For both single and cluster deployments, the
following steps must be taken:

1. Edit the isiq script to set the BACKUP_DIR variable in the User
Configuration section at the top.

2. Make sure the user running the script has write access to that directory.

3. Make sure the directory has several GB free space to hold the backups.

4. Only root has access to the Docker volume locations, so the user running
the script must have sudo access to read and write to those locations. Update
your sudoers file with a line similar to (replace username with the name of
the user running the isiq script):

username ALL=(ALL) NOPASSWD: /bin/tar, /bin/ls, /bin/rm

For a cluster deployment, volumes will need to be backed up on the member
nodes. The same path for the backup directory will be used on all nodes,
so repeat steps 2-4 on all nodes. To automate the backup and restore, the
user running the isiq script must have ssh access to these member nodes.  

5. On the machine where the isiq script is running, run the following commands:

$ ssh-keygen -t rsa
 - Make sure to leave the passphrase empty
 - This will generate an SSH key for the user running the isiq script

$ ssh-copy-id node
 - Replace node with the name of your member node
 - This will copy the public key to the member node to allow SSH access
 - Repeat for each of the hostnames listed with "docker node ls"
 - Copy and paste the following command to generate just the hostname values:
docker node ls | tr -d '*' | grep -vE " VER|$(hostname)" | awk '{ print $2 }'

