Requirements for Eon Mode Databases

Backing up and restoring work the same way in Eon Mode as they do when backing up an Enterprise Mode database to S3. Because Eon Mode uses a different architecture, there are some additional requirements.

Backup and restore are supported for communal-storage locations that use the S3 protocol, but not other storage locations such as HDFS.

Configuration Files

You must back up Eon Mode databases to AWS S3 or S3-compatible storage such as an on-premises data store that supports the S3 protocol. Therefore, you must set values for s3_backup_path and s3_backup_file_system_path in the vbr configuration file. A backup path is valid for one database only; you cannot use the same path to store backups for multiple databases.

If your database runs on-premises, you can still back up to AWS S3; you are not restricted to on-premises backups.

For more about these configuration parameters, see [S3].

Configuration for Databases Running on AWS

In addition to having access to the S3 bucket used for the database's communal storage, you must have access to the S3 backup location. Verify that the credential you use for access to communal storage also has access to the backup location. For more information about configuring S3 access for Vertica, see Configuring Backups to and from S3.

While your backup location may be in a different region, backup and restore operations across different S3 regions are incompatible with Virtual Private Cloud (VPC) endpoints.

Configuration for Databases Running On-Premises Using S3

If your database runs on-premises, then your communal storage is not on AWS but on another storage platform that uses the S3 protocol. This means there can be two endpoints and two sets of credentials, depending on where you back up. This additional information is stored in environment variables, not parameters in the configuration file.  See Backing Up an On-Premises Database.

Backups of Eon Mode on-premises databases do not support AWS IAM profiles.

Eon Mode on-premises databases support the following vbr tasks: backup (full only), restore (full or subset), listbackup, quick-check, full-check, quick-repair, collect-garbage, and remove.

Database Configuration

When restoring a backup of an Eon Mode database, the restore database must satisfy the following requirements:

  • Share the same name as the backup database.

  • Have the same number of nodes as the backup database.

  • Have the same node names as the nodes of the backup database.

  • Use the same catalog directory location as the backup database.

  • Use the same port numbers as the backup database.

  • For object restore, have the same shard subscriptions. If the shard subscriptions have changed, you cannot do object restores but can do a full restore. Shard subscriptions can change when you add or remove nodes or rebalance your cluster.