05 Data management

Backup

Data

Make regular backup of the following.

1. Sync database (logical or physical).
2. datadir directory.

Configuration

Backup the following before and after their contents are modified.

1. conf directory.

Migration

WARNING: Do not attempt any of the below mentioned migration activities while the application is online as it may result in data corruption and/or data inconsistency.

Data directory

Move the directory pointed to by datadir configuration key in the conf file to new location. Update datadir configuration key in the conf file to new location.

Cache directory

Move the directory pointed to by cachedir configuration key in the conf file to new location. Update cachedir configuration key in the conf file to new location.

Sync database

The below mentioned steps can be used to migrate existing sync database data (source database) to a target sync database containing database structure and column types compatible with source database.

Creating SQL dump

1. Create data-only SQL dump of source database excluding below mentioned tables. Use native database tools for the same.
   cards_user
cards_system_user

2. In case you cannot disable foreign key enforcement in the target database during load you, as an example, can create the SQL data dump in a file called ldap_carddav_data_dump.sql (in the current directory) as below to load the data in the target database without getting foreign key violation error(s).

MariaDB / Mysql

1. Create SQL dump of only cards_addressbook table.
   mysqldump --skip-triggers --no-create-info --no-create-db --single-transaction --complete-insert --skip-set-charset --skip-extended-insert --skip-opt --compact --quick --hex-blob --compatible=ansi --skip-quote-names -u <username> <dbname> cards_addressbook | grep -i '^\s*INSERT\s\+INTO\s\+' > ldap_carddav_data_dump.sql

2. Create SQL dump of rest of the needed tables.
   mysqldump --skip-triggers --no-create-info --no-create-db --single-transaction --complete-insert --skip-set-charset --skip-extended-insert --skip-opt --compact --quick --hex-blob --compatible=ansi --skip-quote-names --ignore-table <dbname>.cards_addressbook --ignore-table <dbname>.cards_user --ignore-table <dbname>.cards_system_user -u <username> <dbname> | grep -i '^\s*INSERT\s\+INTO\s\+' >> ldap_carddav_data_dump.sql

PostgreSQL

1. Create SQL dump of only cards_addressbook table.
   pg_dump --format plain --data-only --no-owner --no-privileges --large-objects --inserts --column-inserts --no-comments --no-publications --no-sync --no-tablespaces --no-table-access-method --table <schema>.cards_addressbook --dbname <dbname> | grep -i '^\s*INSERT\s\+INTO\s\+' > ldap_carddav_data_dump.sql

2. Create SQL dump of rest of the needed tables.
   pg_dump --format plain --data-only --no-owner --no-privileges --large-objects --inserts --column-inserts --no-comments --no-publications --no-sync --no-tablespaces --no-table-access-method --exclude-table <schema>.cards_addressbook --exclude-table <schema>.cards_user --exclude-table <schema>.cards_system_user --dbname <dbname> | grep -i '^\s*INSERT\s\+INTO\s\+' >> ldap_carddav_data_dump.sql

SQLite

1. Create SQL dump of only cards_addressbook table.
   sqlite <syncdb_file> '.dump' | grep -i '^\s*INSERT\s\+INTO\s\+cards_addressbook' > ldap_carddav_data_dump.sql

2. Create SQL dump of rest of the needed tables.
   sqlite <syncdb_file> '.dump' | grep -i '^\s*INSERT\s\+INTO\s\+' | grep -iv '^\s*INSERT\s\+INTO\s\+\(cards_addressbook\|cards_user\|cards_system_user\)\s\+' >> ldap_carddav_data_dump.sql

Loading SQL dump

1. Load the ldap_carddav_data_dump.sql file in target database.

Application

When moving the application from one system to another install the same version of the application in the new system. Restore data and configuration from your backup to the new system. Optionally copy cachedir directory (if using 'local_fs' as the caching backend) from the old system to the new system.