The following primary customizations are available through values fed to the
domino-data-importer helm chart:
Importer command-line arguments (The importer is the program that performs the backup. Typically, you do not have to customize this component.)
Use the helm chart value
backups.schedule to change the interval at which backups are performed. This is fed to a Kubernetes CronJob object.
The default value is
@daily, and any valid Kubernetes CronJob schedule string will work, for example:
0 */4 * * *. The string mimics standard cron syntax.
backupJobScript helm chart value to customize the command that creates the backup bundles. The default command line arguments are:
/app/importer -c /app/config-4x-example.yaml -b --backup-archive --backup-upload --backup-delete --backup-strategy BACKUP_STRATEGY
Use the following argument,
(--backup-strategy BACKUP_STRATEGY) to define the strategy to back up large-storage services (such as blobs).
small: Backs up databases and Git only.
transfer: Same as small, but includes a best-effort attempt to setup configuration files for remote import.
large: Backs up everything (such as blobs) by pulling them locally from
nfs/s3. Do not use in production.
transfer strategy adds options to the backup bundle’s importer configuration to copy blobs and other s3-stored data during a backup restore. This is useful if you are restoring to a new Domino deployment while the old one still exists. This is for advanced usage only. Do not use the
large backup strategy because backing up the blobs, registry, and datasets into the bundle will become too large for even modest size Domino deployments. The
large strategy is only useful for testing on development deployments.
You can also remove
--backup-delete for testing or debugging purposes because the argument backups are typically removed from local storage after upload. Removing the argument leaves the working directory for a backup intact, so you can troubleshoot the state of data prior to upload.