Data Backup

From AgileApps Support Wiki

Backup Data from Longjump

As a Customer Support Agent, perform the following steps to get the customer data backup from the Longjump tenant as per their requirement.

Prerequisites

Ensure to have the following handy to start the data backup process:

  • Tenant ID
  • Tenant Name
  • Object(s) that the customer needs a backup of? Or do they need a backup of all the objects?
  • Longjump Server must be up and running
  • Access to the support resources for login and backup, if not the customer must provide their credentials for the same.

Steps

  1. Log in as a Customer Support Agent.
  2. Select the View as tenant view with a name (The view name could be similar to this).
  3. Enter the tenant ID or tenant name in the search bar if available. It will be visible in the view.
  4. Click the folder icon next to the tenant name or ID and the tenant record appears.
  5. Scroll down to see the Customer Support Login as the option.
  6. Click the Customer Support Login option.
  7. A pop-up appears saying that the action will be logged. Click OK.
  8. You will be logged in as a proxy to the tenant.
  9. Go to Settings > Data Management > Export Data. You can see all the objects that can be exported.
  10. Enter your email ID and select the objects from which you want to export the data.
    Note: Select only three to five objects at a time. Selecting many objects takes much time to be exported and the repository does not support so many objects to be packaged.
  11. The exported data is in the ZIP format starting with db-backup{date}.
  12. Unzip the archive folder to verify that the data of the system is present in CSV format.
  13. Provide the ZIP file to the customer as their data.

Notepad.png

Note:

  • There could be multiple ZIP files with data since you would be exporting it for the customers in batches. Hence, make respective customer folders before the backup.
  • Also, ensure that the customer backups are taken one after the other. Do not initiate multiple backups, back to back, or else it would cause problems with data.