Database and Data Backups

Follow

Acoustic Service User

• August 16, 2022 14:45

Is there a way to configure recurring backups of the schema and data in our Acoustic campaign's Databases and Relational Tables, as well as backups of the Import Jobs?

This is a pretty important base to cover for my company, as it would be devastating if we lost all of the work we have in Acoustic.

1

• 

  Karen Buxton

  • August 22, 2022 01:00

  If your data only exist in Acoustic Campaign then I suggest using the API to export it. There is no recurring export. If it comes from another source system then there may already be backups in place?

  1

  Comment actions Permalink
• 

  Data Management

  • August 22, 2022 12:58

  Thanks for your response Karen Buxton, I'll look into which API endpoint I'll need to use to export the data. Do you know if there are any plans on Acoustic's roadmap to implement a recurring export natively?

  0

  Comment actions Permalink
• 

  Geoff Schemel

  • August 24, 2022 03:36

  You can make copies of a database within Acoustic Campaign, this would preserve the state of the database as it currently exists and is often good enough if another user changes the database schema or deletes a bunch of records.

  If you'd like to pull data out of Acoustic Campaign, you could do an export manually. The export would be in a delimited format, like a CSV and would retain the column headers. However it wouldn't be a true "schema" per se. This is usually enough to reimport when needed.

  You could also use an ExportList API to pull the data. You may also want to include a "GetListMetaData" API call as that would return a listing of the fields as well as the field types.

  1

  Comment actions Permalink
• 

  Data Management

  • August 24, 2022 12:36

  Thank you for your response Geoff!

  0

  Comment actions Permalink

Please sign in to leave a comment.