Database Export


Note: When downloading a database export, be aware that you may be downloading PHI. Proceed with caution and insure that the appropriate disk-level encryption and access controls have been established prior to downloading an export.

The db export command allows you to export and download the current users, ACLs, schema, and data from your running database. To use the db export command:

$ datica -E "<your_env_name>"  db export <service name> <local file path>

The filename should be a path to a file (which will be created if it does not exist), not a directory. Example:

$ datica -E "<your_env_name>"  db export db01 ./mydbdownload.sql

For Postgres and MySQL databases, the download will be an SQL file, and for MongoDB, the download will be a gzipped tarball (.tar.gz).

Note: Database exports are a full backup of your database, meaning that they contain users and permissions as well as schema and data. This means that you should not use the db import command to pull in a downloaded export into your database.

Exporting a database is like making and downloading an immediate backup, and follows the same process listed there.

See also

Cloud computing for healthcare

If you store, process, or transmit Protected Health Information, rely on Datica to keep you HIPAA compliant with our platform as a service, mobile backend, or managed HL7 integrations.

Contact Us Learn More

Datica learning resources

Learn the important and intracate details of HIPAA compliance, make use of HL7, and understand the security aspects of handling protected health information with our learning resources.

Visit Datica Learning Resources