You can back up Data Repository to a remote host.
We recommend that each Data Repository node have its own remote host for backups. For example, for a cluster environment with three Data Repository nodes, each Data Repository host requires a dedicated backup host.
Important! For cluster environments, perform the following steps on each remote host that you plan to use to back up each cluster node. Each node in a cluster must be backed up.
Follow these steps:
useradd database_admin_user -s /bin/bash
For example:
useradd dradmin -s /bash/bin
Note: Create the same Vertica Linux database administrator user on the remote backup host that exists on the Data Repository host. Be sure that the Data Repository host and the remote backup host are not connected to LDAP or the Network Information Service (NIS) and sharing the same Vertica Linux database administrator user.
passwd database_admin_user
For example:
passwd dradmin
mkdir /opt/vertica/bin
mkdir /opt/vertica/oss
chown -R dradmin /opt/vertica
ssh-keygen -N "" -t rsa -f ~/.ssh/id_rsa cp ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys2 chmod 644 ~/.ssh/authorized_keys2
ssh-copy-id -i dradmin@backuphost
scp dradmin@<drhost>:/opt/vertica/bin/rsync /opt/vertica/bin scp -r dradmin@<drhost>:/opt/vertica/oss/python /opt/vertica/oss
mkdir backup_directory
Indicates the directory where you want to back up Data Repository to. Select a backup directory that is on a disk partition with a large amount of free space. If these directories are not writable by the database administrator user, give this user access to these directories through utilization of the chown and chmod commands.
Note: In a cluster installation, create the backup directories before you back up the database. You can choose a different backup directory for each host.
For example:
mkdir ~dradmin/backups
Copyright © 2015 CA Technologies.
All rights reserved.
|
|