How to Export Veeam Backup for Salesforce Data to Cloud Storage

This article covers vbsf-export, a standalone utility that exports Salesforce backup data from a Veeam Backup for Salesforce deployment to cloud storage. The exported files can then be used, for example, with the Data Import feature of Veeam Data Cloud for Salesforce to migrate the backup history to the cloud.

With vbsf-export, backup data is exported from the PostgreSQL database managed by Veeam Backup for Salesforce to Azure Blob Storage or Amazon S3. The utility is distributed and installed separately from Veeam Backup for Salesforce, and is compatible with version 3.2.0 or later.

• All parameters can be passed as CLI flags (--property=value) or as uppercase environment variables.
• When the utility is run with no arguments, -h, or --help, the full parameter reference is printed.
• For validation, --test_run=true can be added to check connectivity and show which tables match the configured filters, without exporting any data.
• By default, only start and finish status is shown in the console; details are written to the log files specified in the log_output parameter (vbsf-export.log and debug/vbsf-export.log). To stream full progress to the console instead, --follow (-f) can be added.
• Salesforce object names are mapped to lowercase table names in the backup database. To also include Account's history, --export_table_filter='^account(__h)?$' can be used.

Example

In the following example, only the Account object's data, changed on or after June 1, 2025, is exported to Azure Blob Storage:

java -jar vbsf-export.jar \
  --jdbc_url=jdbc:postgresql://localhost:5432/vbsf_application \
  --jdbc_username=vbsf --jdbc_password=*** \
  --sf_org_id=00D2C000700gi2SUAQ \
  --azure_account_name=mystorageaccount --azure_access_key=*** \
  --azure_container_name=vbsf-export \
  --log_output=/var/log/vbsf/vbsf-export \
  --export_table_filter='^account$' \
  --filter="vsf_last_modified_date >= '2025-06-01 00:00:00+00'"

• Salesforce object record data (current state and history restore points) is exported from the backup PostgreSQL database to Azure Blob Storage or Amazon S3.
• Everything can be exported, or the run can be limited to specific Salesforce objects by matching table names with a regular expression (by default, every table is exported).
• Only a date range can be exported instead of the full history: a SQL condition (for example, "modified on or after a given date") can be applied to all exported tables, or overridden for a specific table.
• Output can be produced as plain CSV, GZIP, ZIP, or password-protected ZIP, with optional file splitting by row count or size.
• A test-run mode is available to validate the configuration before real data is exported.

• Only Salesforce object record data is exported; Files, Attachments, and metadata are not supported.
• Data is not decrypted, so encrypted fields are excluded by default. If the decrypted data is required (for example, to perform Data Import into Veeam Data Cloud for Salesforce), the fields must be decrypted beforehand.
• Data is streamed directly to cloud storage, so a stable connection from the export host to the storage endpoint is required for the entire run.
• If a column referenced by a row filter does not exist for a table (or causes a type mismatch), that table is skipped with a warning in the log, and the remainder of the export continues.