Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The CapStorm/Container provides Salesforce replication, backup, and recovery – copying Salesforce data and structure to a relational database and recovering data to Salesforce production or sandbox environments.
This application runs as a Docker container and exposes core CapStorm applications and functionality via a web server.
To access the CapStorm/Container, contact support.
The Home Page provides a simple way to look at all jobs that have been created, the status of the jobs, as well as the ability to see more information about the job including the tasks and task history by clicking the job in the table.
Release Date: 19-Dec-2025
This is a feature and bug fix release. As always, existing CapStorm/Container installations are backwards compatible.
19-Dec-2025
Original Release
The CapStom/Container now comes with a data recovery feature that can be used to upload record data from database to Salesforce.
New environment variables have been added to the CapStorm/Container to provide default SMTP configuration. If environment variables are provided, they will be used as default values in CapStorm applications (and can be overridden in individual configuration files).
Base64 / File Export Fix
Resolved an issue with the CopyStorm/Medic Base64 Export tool that could cause the exported zip file to be unreadable on Windows.
Data Viewer Filter Enhancement
Updated the Data Viewer to support OR filters.
Salesforce Username Length Change
Increased the maximum allowed length of a Salesforce Username to 200 characters.
CopyStorm: 10.64.3
CopyStorm/Medic: 10.64.3
CopyStorm/Restore: 10.64.3
CopyStorm/Director: 2.64.3
This stage is where you review exactly what happened during the restore, broken down by Salesforce object and record. Use it to confirm success, investigate errors, and understand why anything was skipped.
At the top of the page are filters that control what shows in the results grid:
Object – chooses which Salesforce object’s restore results you’re viewing
Fields – chooses which columns/fields are shown in the grid
Record Type – filters results by outcome/status (details below).
On the right side are action buttons:
Export – downloads the currently viewed results (based on your selected object/filters/fields).
Show Errors – opens a view/list of error details (use this first when something failed).
Show Skipped Reasons – shows the reasons records were skipped (super helpful for “why didn’t it restore?” questions).
Previous Step – go back if you need to revisit earlier stages.
Select the object you want to analyze (Account, Contact, etc.). This page shows results one object at a time, so you’ll typically bounce between objects when validating a large restore.
Use this to control which columns appear in the grid.
Keep it small when you’re troubleshooting (ID + name + status + a couple key fields).
Add more fields when you need to verify that specific values restored correctly.
This filters the grid based on restore outcome. Options are:
All – shows everything.
Pending – records that are still being processed (mostly useful if you open View Results before the restore is fully finished).
Skipped – records that were not restored (use Show Skipped Reasons to see why).
Inserted – records that were created in the target org.
Common columns you’ll see:
Original Id – the record ID from the backup/source dataset.
Restored Id – the record ID in the target org after the restore.
For Inserted records, this may be a newly created ID.
For Updated
Set Record Type = Errors
You don’t have an “Errors” option in the dropdown, so instead click Show Errors to view the error details directly.
Fix the root cause in Salesforce (common themes: validation rules, missing required fields, permissions, duplicate rules).
Return here to confirm the error count dropped and records moved to
For skipped records:
Set Record Type = Skipped
Click Show Skipped Reasons
Look for patterns (restore type mismatch is the classic one: Insert Only skips “already exists”; Update Only skips “does not exist”).
Use Export when you need to:
Share outcomes with a team/customer
Track what changed
Save the restore output for audit/review
Tip: Apply Object + Record Type filters first so the export is focused and readable.
The Salesforce Credentials page allows fast and easy registration of Salesforce Credential(s) associated with the Org(s) to be backed up.
Note that the logged in user must be, at minimum, an Admin CapStorm Role to update credentials. See User Security for more details on CapStorm Roles.
To register new Salesforce Credentials, click the Add New Credentials button. You will be presented with the dialog below to provide credential information. Use the Test Connection button to validate that the input credential information can successfully connect to Salesforce.
To edit existing Salesforce Credentials, click the Edit icon in the “Click To Edit” column of the desired credential to edit. You’ll be presented with a dialog to update credential information:
Next Step – proceed to Summary after you’ve reviewed results.
Updated – records that already existed in the target org and were modified.
Status – the outcome for that record (Inserted / Updated / Skipped / Pending).
Additional columns (like Account Name, timestamps, audit fields, etc.) depending on your Fields selection.
Username & Password
Traditional Salesforce Username & Password authentication. Provide inputs for Username, Password, & Security token. Note that a security token may also be required depending on your Salesforce’s security configuration. Passwords are always encrypted.
The job viewer page allows a user to see more information about a selected job from the Jobs table on the Home page. The Job Viewer contains two sections: Job Tasks and Job History.
The Job Tasks section of the Job Viewer page displays information about the tasks that run under the selected job including the task type as well as the configuration profile used for the task. As well, the next run time and the schedule for the task are displayed. It is important to note that the schedules displayed are in UTC, while the next run times are displayed in the local time.
The Job History section of the Job Viewer page displays information about previous runs of tasks in the selected job. By default, task executions going one week in the past are displayed, but more (or less) information can be displayed using the History From and History Through options.
The CapStorm/Container reference provides documentation on available settings and features within the CapStorm/Container.
To install the CapStorm/Container, you will need to have a container host ready to run the container.
This installation guide provides an example installation path using the Docker Desktop application.
Pull the latest image from the capstorm/capstorm docker repository.
Configure port forwarding to enable web access. CapStorm/Container web services are hosted via Apache Tomcat, which consumes the following ports:
Container port 8080 provides HTTP access.
Container port 8443 provides self-signed HTTPS access.
Start the container.
Navigate to the container’s web URL ().
If the image has successfully launched, you will see a screen that looks like this:
Once the container is launched, log in with the following credentials:
Username: capstorm
Password: capstorm
To configure initial container parameters, click on the Click Here for Initial Configuration link:
After Clicking the Click Here for Initial Configuration link, you will see a screen that looks like this:
When initialization parameters have been provided, click Validate Configuration to validate the provided customer key & database connection.
After a successful save you’ll see the following dialog:
Refer to the comprehensive for in-depth insights into various components of the web application.
Configuration files from the desktop version of CapStorm applications can be imported into the CapStorm/Container by following this process:
Open the CapStorm application.
Click on File -> Import in the top left of the application.
Select the configuration file on your local computer.
Press File -> Save to save the configuration.
After saving the configuration, you can use CopyStorm/Director to create the job schedule.
Go to the “Applications” tab and select the CapStorm application.
In the top-left, select File -> Import.
In the pop-up, select Browse.
Find and select the application configuration file – CopyStorm configuration files end in “.copyStorm”.
After saving the configuration file, you can schedule the configuration using CopyStorm/Director.
This is the final step of the wizard. It gives you a high-level report of the restore job: what ran, where it restored to, how many records were restored/skipped/errored, and an activity log you can use for auditing and troubleshooting.
The Details panel summarizes the restore job configuration you ran:
Name – the restore job name you entered in Configuration.
Parent Object – the top-level object you restored (example shown: Account).
The Access Control tab is used to configure access control/authorization for core CapStorm applications (CopyStorm, CopyStorm/Medic, CopyStorm/Restore, and CopyStorm/Director). The Access Control editor table can be used to add new and edit existing CapStorm application users and assign pre-defined roles to users. These pre-defined roles will determine the level of access (available functionality) granted to the assigned user when using the aforementioned supported applications.
Click on the “Add User…” button.
This will open a pop-up dialog where you can enter the following:
Username — a unique username.
Password — a strong password.
Release Date: 22-Aug-2024
This is a dependency, CapStorm Application, and Salesforce API version upgrade release. As always, existing CapStorm/Container installations are backwards compatible.
22-Aug-24
Original Release
Data Viewer: Fix for queries to Percentage Fields
Fix issue where data viewer allowed to query with ‘contains’ operator against percentage fields
This container includes CapStorm applications:
CopyStorm 10.59.3
CopyStorm/Restore 10.59.3
CS:Medic 10.59.3
CopyStorm/Director 2.59.3
Third-party Authentication:
Salesforce Username
Authenticator URL
Client Id
Client Secret
no
Use these parameters to authenticate with the CapStorm/Portal using a Salesforce username and password.
Connection String
yes
JDBC Connection String used to connect to the CapStorm/Portal configuration database. For initial configuration, this should point to an empty schema – the CapStorm/Portal will bootstrap all required schema elements.
JDBC Driver
yes
JDBC driver used to connect to the CapStorm/Portal configuration database.
Username
yes
JDBC username used to connect to the CapStorm/Portal configuration database.
Password
yes
JDBC password used to connect to the CapStorm/Portal configuration database.
Customer Key
yes
CapStorm-provided identifier, used for licensing.
Admin Password
yes
The password for the “Admin” username. After initializing, the “CapStorm” user is no longer available and the “Admin” username will be used.
Source Connection – the backup database/source used for the restore (example shown: PostgreSQL).
Type – restore type used (example shown: Insert And Update).
Target Connection – the Salesforce org connection restored into (example shown: Sandbox).
Use this section as your “receipt” to confirm:
You restored the right object(s),
From the right backup source,
Into the right Salesforce org,
Using the intended restore mode.
This panel gives an at-a-glance breakdown of restore outcomes using a pie chart and counts.
There’s a dropdown above the chart (example shown: All Objects) that lets you switch between:
A combined view across everything restored (All Objects), or
A specific object view (useful if one object had lots of skips/errors).
The results are grouped into three buckets:
Restored – records successfully written to Salesforce (inserted and/or updated).
Skipped – records not written due to restore rules or conditions.
Errors – records that failed due to Salesforce/API/validation/permission issues.
Next to Skipped and Errors you’ll see Click to view links. Use these to jump directly into the underlying details (so you can see which records were skipped/errored and why).
A lot of Skipped can be normal depending on restore type (Insert Only / Update Only) and the state of the target org.
Any meaningful Errors should be reviewed-errors mean Salesforce rejected changes or the restore couldn’t complete operations as planned.
The Activity Log is a timeline-style log of what happened during the restore (status updates, steps, notable events).
You can filter the log by time window:
All Time
Last Year
Last Month
Last Week
Use this when:
You run multiple restores and want to isolate the relevant one,
You’re comparing outcomes across runs,
You’re troubleshooting something that happened recently.
Entries are grouped (example shown: Today) and show how many log entries exist for that period.
Before clicking Finish:
Check the Details panel to confirm you restored into the correct target org.
Review the Records Restored breakdown.
Click into Errors (and Skipped, if unexpected) to confirm you understand the outcomes.
Use the Activity Log time filter if you need to capture troubleshooting notes for support/audit.
CopyStorm will auto-populate with the imported configuration.
In the top-left, select File -> Save.
Role — Three pre-defined roles are available:
Super Admin — a top-level administrative role. A user with this role can perform any operation in any application including configuration of Access Control.
Admin — a slightly restricted administrative role. A user with this role can perform any operation in any application except configuration of Access Control.
Configurator — a user with this role can edit configurations for all applications except CopyStorm/Director, but cannot invoke any of the applications (cannot run jobs).
Production Enabled — this checkbox determines whether the user will be granted Access against Production Salesforce Instances.
The “Production Enabled” check-box will enable/disable any operation that is allowed by the assigned role against a production database or Salesforce org. For example:
A user that has been assigned the “Configurator” role but has the “Production Enabled” check-box unchecked cannot edit a production configuration.
Then click the “Save” button to add the user.
When you are finished making changes to the Access Control configuration, click the “Save” button at the bottom of the editor table. A pop-up dialog will appear where you can validate and save or cancel all staged changes.
You can also undo all staged changes by clicking the “Cancel” button.
To install the CapStorm/Container, you will need to have a container host ready to run the container.
This installation guide provides an example installation path using the Docker Desktop application.
Note: To install the container using Docker Compose (CLI), please refer to CapStorm’s docker hub for an example.
A Host For the Docker Container
A CapStorm Customer Key GUID
The CapStorm team will provide you with a unique Customer Key associated with your account. This key provides access to your entitled features. The CapStorm customer key will take the following form:
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Valid database connection details to a MySQL, PostgreSQL, or SQL Server database
The CapStorm Platform database user is expected to have the following Database Permissions
CONNECT
Used to establish remote connections to the target database
If your organization wishes to use Salesforce as an Authenticator for CapStorm/Container, be sure to follow our guide for
Pull the latest image from the docker repository
This can be accomplished by searching for the image in Docker Desktop and clicking Pull. Note that the latest GA release of the CapStorm/Container will have the tag latest.
In Docker Desktop, navigate to Images
Click the Play Icon to queue up the container launch
Before clicking the Run button, expand optional settings. You’ll see the following screen:
Use this screen to provide:
After providing all previously mentioned environment variables, the image is ready to launch. Click the Run button to start the container.
The screenshot below is an example of an image launch:
Note: The container bootstrapping process is completed once you see the following message in the Container Logs:
CopyStormDirector is waiting for 0 jobs to complete.
Note: The following message will be displayed in the Container Logs if there are issues establishing a connection with the Database:
Exception in thread “main” java.lang.Exception: Cannot connect to database.
at com.capstorm.platform.configuration.webconfig.a.b(SourceFile:260) at com.capstorm.platform.environmentinitializer.EnvironmentInitializer.c(SourceFile:175) at com.capstorm.platform.environmentinitializer.EnvironmentInitializer.b(SourceFile:415) at com.capstorm.platform.environmentinitializer.EnvironmentInitializer.main(SourceFile:441)
Note: The following message will be displayed if there were any issues bootstrapping the CapStorm/Container:
Error running scheduled CopyStorm/Director jobs
In a Web Browser, navigate to or
You will see the following screen:
If you did NOT provide initialization environment variables: log in with the temporary bootstrap credentials capstorm / capstorm, then click “Click Here for Initial Configuration” and complete the setup wizard (Customer Key, Admin Password, database connection, etc.).
Please refer to the Reference Documentation for the CapStorm/Container and core CapStorm Applications:
Backup Salesforce to a Relational Database
The Quick Start Backup page allows fast and easy configuration of best-practice Salesforce replication.
Before configuring the Quick Start Backup, please be sure to address the following prerequisites:
Configure Salesforce Credentials in the Salesforce Credentials section.
Configure Database Credentials in the Database Credentials section of the navigation menu
If a database is not readily available, you may create one in the Database Management section
After clicking Save Changes, the following will be created in the CapStorm Applications:
**CopyStorm:**Two CopyStorm Configuration Files will be created
Quick Start Data
Copies most Salesforce Standard objects, excluding certain File objects such as ContentVersion & Attachment.
Quick Start Files and Metadata
By Clicking on the “Best Practice Disaster Recovery” Job Name, you’ll see the following tasks configured within the job:
For additional information on CopyStorm/Director jobs & scheduling, please refer to .
The CapStorm database management sub-system supports the creation of databases for use with CapStorm applications. Common use cases include:
A CopyStorm database to store a Salesforce backup.
A CopyStorm/Restore tracker database, which contains information about records that can or will be restored.
To create a new database, click the Create Database button in the top right of the page. This will open a small panel that allows input for information about the database. An example of this window can be seen below:
The following input parameters are used to create the new database:
**Name:**The name of the database to create
Usage: How the database will be used for CapStorm applications
CopyStorm: Stores SFDC data in tables
CopyStorm/Restore Tracker: The backing database for restore processing used to track state of upserted records
The Applications tab serves as a dedicated interface for launching the core CapStorm Application Suite, including:
To launch any application, click the Application Icon to the left of the Application Name.
The CapStorm/Container stores configuration and scheduling data in a CopyStorm/Director Database. The database is initialized when the CapStorm/Container first connects.
You can configure the database connection by either:
Providing environment variables with connection information.
Setting the connection information on the Initial Server Configuration tab.
After the connection information is provided, the container will alter the database to match by creating tables and columns as defined in the Director Database schema. All tables, including those denoted (Platform Only), are a part of the CopyStorm/Container backing database.
The Restore Wizard guides you through restoring Salesforce data from a CopyStorm backup stored in your CS:Container database back into a target Salesforce org. It walks you step-by-step through selecting records to restore, configuring how the restore should behave, scanning for candidate records, uploading records, and then reviewing detailed results and a final summary.
Use this workflow to recover data, correct unintended data changes, or selectively restore a subset of records to production or sandbox.
Step 1: Select Records — select the object and records that will be uploaded to Salesforce.
Step 2: Configuration — configure data upload parameters (insert/update behavior, related record depth, automation handling).
— query the database for records matching the restore criteria.
— insert or update candidates into the target Salesforce.
— view record upload results.
— view an overview of record restore activity.
The Database Credentials page allows fast and easy registration of Database Credential(s) associated with the database where the CopyStorm Backup(s) reside.
Notethat Built-In credentials have been pre-installed. These are the database credentials to the underlying CapStorm Platform database.
Note that the logged in user must be, at minimum, an Admin CapStorm Role to update credentials. See User Security for more details on CapStorm Roles.
To register new Database Credentials, click the Add New Credentials button. You will be presented with the following dialog to provide credential information:
To edit existing Database Credentials, click the Edit icon in the “Click To Edit” column of the desired credential to edit. You’ll be presented with a dialog to update credential information:
In order to login to the CapStorm/Container using Salesforce, you will first need to set up a connected app in your Salesforce org. This connected org will need to have OAuth Settings enabled along with a handful of other settings. This article walks through each step required to create a Salesforce Connected App that can be used to enable Salesforce authentication in the CapStorm/Container. For more information on setting up Connected Apps in Salesforce, please visit
Note: the screenshots and instructions in this page use sample values for a number of parameters.
is the host/port used for the CapStorm/Container.
You will need to use the host and port values that are applicable to your environment.
Release Date: 2025-Apr-01
This is a dependency and CapStorm Application upgrade release. As always, existing CapStorm/Container installations are backwards compatible.
Release Date: 16-Dec-2024
This is a dependency, CapStorm Application, and Salesforce API version upgrade release. As always, existing CapStorm/Container installations are backwards compatible.
Description: A description about the database being created
Prevent Deletion: Checking this box means that the created database cannot be deleted
Username & Password
JDBC Username & Password authentication. Provide inputs for Username & Password. Passwords are always encrypted.
CREATE DATABASE
Used to provision databases containing Salesforce Backups
DROP DATABASE
Used to deprecate legacy Salesforce Backup databases
For the Salesforce Backup databases, The CapStorm Platform user is expected to have:
INSERT
DELETE
UPDATE
CREATE / ALTER TABLE privileges
Used to mirror & maintain changes in Salesforce data model
The database can be hosted in a container, or in any major RDBMS hosting platform (e.g. AWS, Azure, GCP, or on-premises)
A name for the container
Host port mappings for ports 8080and 8443
Environment Variables mentioned below
You can start the container with only port mappings (8080/8443). On first launch, the UI will allow initialization via the Initial Configuration setup page.
Temporary bootstrap login (before initialization):
Username: capstorm
Password: capstorm
Provide Environment Variables for Container Initialization
Note: Required Environment Variables are BOLDED.
Note: Required Salesforce Authenticator Environment Variables are ITALICIZED.
CUSTOMER_KEY
CapStorm Customer Key. Provided by CapStorm team members.
ADMIN_PASSWORD
Default CapStorm/Container administrator password. This parameter can be used to initialize the password for the ‘admin’ user – if the admin user is already initialized this parameter has no effect.
EXTERNAL_AUTHENTICATOR
A name for the Salesforce OIDC External Authenticator – usually “Salesforce”.
OIDC_ISSUER_URL
Provide the complete URL of your Salesforce instance for user authentication.
OIDC_ADMIN_USERNAME
Provide the Salesforce username that will be granted administrator permissions for the CapStorm platform app.
OIDC_CLIENT_ID
CONSUMER_KEY value obtained in Prerequisite – Salesforce Authenticator step.
OIDC_CLIENT_SECRET
CONSUMER_SECRET value obtained in Prerequisite – Salesforce Authenticator step.
Username: admin
Password: Value of ADMIN_PASSWORD environment variable from Step (2)
Upon successful login, you’ll see the CapStorm/Container Web UI:
Schedule CopyStorm Jobs
Validate, Maintain, & Repair CopyStorm Databases
Push Data from a CopyStorm Database to Salesforce
DB_CONNECTION_STRING
The connection string to the target database. This database will be used as the backing store for container configuration.
DB_USERNAME
The Database User for the CapStorm container database.
DB_PASSWORD
The Database Password for the CapStorm container database user.
Add environment configuration to disable user/password authentication.
Add environment configuration for customer-provided OAuth authentication.
Fix initialization issue for customer-provided certificate files.
Fix initialization issue for entitlement pre-loading.
Hide “Open in Salesforce” links for records that are marked as deleted.
Update object and field selectors to enable filtering.
Updated CopyStorm/Restore to disable automation enable/disable features for read-only users.
CopyStorm: 10.62.2
CopyStorm/Medic: 10.62.2
CopyStorm/Restore: 10.62.2
CopyStorm/Director: 2.62.2
2025-Apr-01
Original Release
Home:
Job Widget: Introduces a new table on the Home page to show the status of jobs.
Job Viewer: When clicking on a job in the Home page table, the user is redirected to a new page that shows further information about job tasks and job history.
Salesforce Credentials:
Test Credentials Button: Allows a user to test a the connection to Salesforce with the provided credentials when adding or editing the login details prior to saving.
Database Management:
Custom databases: “Custom” databases can now be added. A “Custom” database is a database that already exists, but it being tracked and used by the application. For example – This will enable the transition to the container with a pre-existing CopyStorm setup more easily.
CopyStorm/Director Application:
Log Retention Parameter: Adds a new “Log Retention” parameter that can be applied to CopyStorm and CopyStorm/Medic tasks. This value is an integer that denotes the number of log files to maintain in the database. If the value is left blank, the log retention is infinite.
Data Viewer:
Queries to Percentage Fields: Fixes issue where data viewer allows queries with ‘contains’ operator against percentage fields.
This container includes CapStorm applications:
CopyStorm 10.62.1
CopyStorm/Restore 10.62.1
CS:Medic 10.62.1
CopyStorm/Director 2.62.1
16-Dec-24
Original Release
Backup Schedule
Yes
High Frequency:
Backup data once an hour, backup files and metadata once a day.
Provides improved data fidelity, but uses more Salesforce API calls.
Low Frequency:
Retention Period
Yes
Days of Safety – how long should record changes be kept?
Retain deleted records in the primary CopyStorm data tables for this many days.
Retain Point-In-Time record change history for this many days.
Metadata change history is always retained for 10 years (3650 days).
Notify on Error
No
If a CopyStorm job encounters an error, use the Salesforce user to send an email notification to these recipients. To send an email notification to multiple recipients, separate their emails with a semicolon “;” character.
Copies File objects (ContentVersion, Attachment) & Salesforce Metadata
For more information on CopyStorm Configuration Files, please refer to the linked documentation.
CopyStorm/Director: A CopyStorm/Director Job called Best Practice Disaster Recovery. This job executes the previously mentioned configuration files on a recurring schedule.
The rate of scheduling depends on your choice of High Frequency or Low Frequency from Step 1.
The below image depicts the Best Practice Disaster Recovery CopyStorm/Director Job:
Salesforce Credentials
Yes
Use these credentials to login to Salesforce. To register new credentials, or update existing credentials, select Salesforce Credentials in the navigation menu.
Database
Yes
Select a CapStorm-managed database. To create a CapStorm-managed database, select Database Management in the navigation menu. If you would like to register a pre-existing database, select Custom and provide the database connection information.
Your values for the host, port, and protocol should be used for the Callback URL parameter and the Start URLparameter.
The Connected App Name and contact details should be changed to reflect proper values for your organization.
Login to Salesforce and go to Setup
In the Quick-Find search bar, type App Manager and select it
In the top right, click New Connected App
Enter a name for the app in the Connected App Name field
The API name will auto-fill when you click enter
Note: This name can be anything you’d like
Add a Contact Email
In the API (Enable OAuth Settings) section, select Enable OAuth Settings
In the Callback URL box, enter **
For the Selected OAuth Scopes, add the below scopes
Access the identity URL service (id,profile,email,address,phone)
Access unique user identifiers (openid)
Disable the below settings
Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows
Require Secret for Web Server Flow
Require Secret for Refresh Token Flow
Enable the below settings
Enable Authorization Code and Credentials Flow
Enable Token Exchange Flow
Enable Configure ID Token
Set Token Valid for to 10 Minutes
Select Include Standard Claims and Include Custom Attributes
Under Web App Settings, enter next to Start URL
Click Save
In the API (Enable OAuth Settings) section, click the Manage Consumer Details button
Note the Consumer Key and the Consumer Secret; You will need these for setup in the application.
Consumer Key = OIDC_CLIENT_ID
Consumer Secret = OIDC_CLIENT_SECRET
Release Date: 28-Apr-2026
This is a feature and bug fix release. As always, existing CapStorm/Container installations are backwards compatible.
28-Apr-2026
Original Release
Salesforce API version 65 deprecates the SOAP username/password login endpoint. Customers should migrate to an external client application configured with OAuth. Jobs using a login type that does not support API 65 will automatically fall back to API 64, and an exception will be logged at the start of each job as a reminder to migrate. This exception can not be eliminated until OAuth authentication is used.
The "Fallback API Detected" error does not stop jobs from running - it is informational, and indicates that bundled applications are not able to use the most recent Salesforce API features. The error will be resolved when updating to JWT (or other OAuth) authentication.
Please reference .
The CapStorm/Container now supports three additional credential types for connecting to Salesforce:
OAuth JWT
OAuth Client Credentials
One-Time Password Authenticator
Upgraded bundled applications to use Salesforce API v65.
Addressed all High and Medium severity vulnerabilities identified by Docker Scout.
Resolved a formatting issue with CSV downloads from the Data Viewer.
Fixed an issue where the container bootstrapping process could result in duplicate jobs being created.
Updated the version of Tomcat bundled with the container to 11.0.11.
Folder-Based partitions are now disabled by default to prevent unintended configuration.
CopyStorm: 10.65.1
CopyStorm/Medic: 10.65.1
CopyStorm/Restore: 10.65.1
CopyStorm/Director: 2.65.1
Release Date: 2025-Aug-01
This is a CapStorm Application upgrade release. As always, existing CapStorm/Container installations are backwards compatible.
2025-Aug-01
Original Release
The Job Viewer table now includes a “Task Name” column. This allows you to quickly see which configuration is being used for each job directly from the main view.
The date and time format in the container bootstrap save dialog has been updated for better readability and consistency.
New ‘Between’ Filter for Dates: You can now filter date and date/time fields using a ‘Between’ operator. This allows you to easily select a start and end date in a single filter to quickly find records within a specific range.
A Cancel button has been added to the settings dialog, allowing users to discard changes and close the window without saving.
Updated CopyStorm/Medic to support Base64 Export Tool in container.
Upgrade Salesforce API from v62 to v64.
CopyStorm: 10.64.1
CopyStorm/Medic: 10.64.1
CopyStorm/Restore: 10.64.1
CopyStorm/Director: 2.64.1
The View CopyStorm Data tab serves as a dedicated interface for visualizing and validating your Salesforce data within your CopyStorm backups.
Click on the “Database” dropdown. This will display a list of all CapStorm-managed Database used for Salesforce Backups
This will open a drop down of all available CopyStorm Databases.
Then, optionally provide a Snapshot to view from. The default is the primary CopyStorm Database.
Upon selecting your database, proceed by choosing an object to view from the Object dropdown menu, which encompasses all available Salesforce objects in the database.
Pick one or more fields to be displayed in the results. By clicking the “Show All” checkbox, all fields are shown when querying for records.
This stage is the “sanity check + planning” step. The wizard scans what you selected (records + related depth + field settings) and builds a list of restore candidates. Once the scan finishes, you’ll click Restore to move forward.
When you click Scan Records, the restore wizard:
Evaluates your selected top-level object records (from Step 1)
Applies your Step 2 settings (Restore Type, Object Settings, Related List Depth, Automation choice)
This stage is where you choose what you want to restore-starting from a specific backup (database + snapshot), down to the Salesforce object and the record set you care about. CapStorm/Container’s job is to back up Salesforce into a relational database and support recovery back into Salesforce.
To successfully select records, you generally need:
A running CapStorm/Container environment you can log into. A CopyStorm backup database available/managed in the container. (Databases are typically created/managed under Database Management.)
Database connection info registered (so the container can access the backup database).
Backup data once a day, backup files and metadata weekly.
Minimizes Salesforce API call consumption.
Determines which objects/records are in-scope and counts them as candidates
Prepares the restore job so the next steps can upload/apply the data
You’ll see:
Scan Records button (starts the scan)
Cancel Scan button (enabled while a scan is running)
A grid with:
Status – progress/state of scanning for that object
Object – the Salesforce object being scanned (top-level and/or related objects)
# Candidates – how many records were found that are eligible for restore
Restore button (top-right) – this is what you click after the scan completes to continue
Click Scan Records.
As the scan runs, the table will populate with one or more rows (depending on your related list depth and what relationships exist).
Use the table to confirm the restore scope makes sense.
If you expected “just a handful” and you see a huge number of candidates, your settings are probably too broad (most commonly Related List Depth = All).
If you expected results and candidates are zero, your filters/selection may be too narrow, or you may be restoring the wrong snapshot/object.
If you realize the scan is going in the wrong direction (wrong object, wrong depth, candidate count exploding), hit Cancel Scan, then go Previous Step to adjust.
Once the scan is complete, click Restore to proceed to the next stage.
A candidate is a record the restore job has identified as in-scope for restoration based on your selections and settings.
Candidate count is heavily influenced by:
Related List Depth (None vs 1/2/3 vs All vs Custom)
Your Step 1 Filters
How many related/child records exist in your data model
Go back to Configuration and reduce Related List Depth (try None or 1 Level first).
Tighten Step 1 filters to target a smaller set.
Verify you selected the right Database + Data Set (snapshot) and Object in Step 1.
Loosen filters and re-run the scan.
Confirm you aren’t using Update Only when the target org doesn’t already contain those records (that can result in fewer/no eligible candidates depending on matching behavior).
Big restores are usually caused by deep relationship depth + lots of related data.
Cancel, reduce depth, and re-scan to validate scope before committing.
Salesforce credentials configured in the container (used in later stages when writing back to Salesforce).
The page is split into two main areas:
Left panel: where you define your restore search (Database, Data Set, Object, Fields, Filters).
Right panel: a results grid that previews which records match your criteria (it will show “No Records to Show” until you run a search).
Across the top, the wizard stage tracker shows the overall flow:
Select Records → Configuration → Scan Records → Upload Data → View Results → Summary
In the Database dropdown, select the database that contains your CopyStorm backup data.
If you have multiple backup databases, pick the one that corresponds to the org/data you intend to restore.
In the Data Set dropdown, select the snapshot you want to restore from.
Think of this as your “point-in-time” choice. CapStorm tools commonly treat snapshots as the specific backup set within a database.
In the Object dropdown, choose the top-level Salesforce object you want to start from (for example: Account, Contact, Case).
This object becomes the basis for your search + preview results.
Use the Show Fields tab to control which fields/columns appear in the preview results grid.
This helps you confirm you’re targeting the correct records before moving forward.
If you’re not sure what to include, start with obvious identifiers (Name, Email, etc.) and expand as needed.
Switch to the Filters tab to define criteria for the records you want restored.
Keep filters tight when possible-especially in large orgs-to reduce scanning and make validation easier.
Example filters (conceptually): Name equals “Acme” or LastModifiedDate greater than .
Click Run Search.
Matching records will populate in the right-side results grid.
If nothing appears, loosen your filters (or verify you selected the intended snapshot/object).
Once your preview looks correct, click Next Step (bottom-right) to advance to Configuration.
“No Records to Show” after Run Search
Your filter may be too restrictive, or the selected snapshot doesn’t contain the records you expect.
A quick sanity check is using View CopyStorm Data to confirm the object + records exist in that backup.
Database/snapshot not available
Confirm the database exists/was created for CopyStorm backups in Database Management and that access is configured in Database Credentials.
The following four fields are always displayed by default:
Id
The Salesforce ID of the record
CreatedById
The Salesforce ID associated with user who created the record
LastModifiedById
The Salesforce ID associated with user who last modified the record
SystemModStamp
A timestamp indicating the most recent modification of the record.
Select one or more fields for filtering the queried records.
Field filters support the following comparators:
contains
equals
not equals
greater than
greater than or equal to
less than
less than or equal to
To pull results from your CopyStorm Database, click the Run icon in the top-right:
Once your data is retrieved, the results will be displayed in the data grid:
The CopyStorm Data Viewer provides the ability to export your results to CSV format. This can be achieved by clicking the Export button in the top right.
This process will download a CSV file:
The name of the CSV file takes the following form:
ObjectName_SnapshotName_Database_CurrentTimeStamp.csv
To view a single record, you can click directly on any Salesforce ID field that is highlighted.
An example is shown below:
Clicking Directly on the Salesforce ID will open a new tab in the CapStorm/Container Web UI displaying the single record. An example of a Single Row View is shown in the image below:
To open a single record in Salesforce, you can click directly on the “Open In Salesforce” icon directly to the right of the Salesforce ID
An example is shown below:
Clicking Directly on the “Open in Salesforce” icon will open the record in Salesforce in a new tab.
Note: This icon will be displayed even if the record has been deleted in Salesforce
Navigate to the Data Viewer Settings by clicking Settings in the top-right
Clear Metadata Cache
The CopyStorm Data Viewer stores CopyStorm database schema information locally in your browser to improve performance. If fields or objects that are present in your database are not available in the data viewer UI, you can press this button to clear the local browser cache. After pressing this button, the CopyStorm Data Viewer will update with the latest object and field information from the database.
This stage defines the high-level restore job configuration: what the job is called, which Salesforce org you’re restoring into, how the restore behaves (restore type), and a few “be careful with this” options like field selection/masking, related record depth, and Salesforce automation behavior. CapStorm/Container is built for Salesforce backup + recovery workflows like this.
You should already have selected the Database / Data Set (snapshot) / Object / record set in Select Records.
Make sure the target Salesforce Org credentials exist in the container, otherwise the Salesforce Org dropdown won’t have anything to pick.
Give the restore job a clear name you’ll recognize later (example: Restore Accounts – Sandbox QA – 2025-12-16).
Optional, but useful for notes like why you’re doing the restore or what filters were used.
Controls how the restore writes records into Salesforce.
Inserts records that don’t exist in the target org.
Updates records that already exist in the target org.
Best choice for “bring my data back” restores when you’re not 100% sure what already exists.
Only inserts new records.
Does not modify existing records.
Use when you’re loading data into an org and you want to avoid overwriting anything already there (common for seeding sandboxes / partial restores).
Gotcha: If records already exist (based on whatever matching/key logic is used later in the wizard), they’ll be skipped rather than updated.
Only updates records that already exist in the target org.
Does not create new records.
Use when you’re correcting or reverting fields on records you know are already present.
Gotcha: If a record doesn’t exist in the target org, it will not be created-so you can end up with a partial restore if your assumptions are wrong.
Select the target Salesforce org where data will be restored.
This list is populated from entries you’ve configured under Salesforce Credentials.
If this dropdown is empty, go set up credentials first.
Controls which fields are included in the restore for the top-level object (and how much control you want).
Restores all supported fields for the object.
Best for full-fidelity restores.
Lets you choose exactly which fields to restore.
Use when:
You only need a few fields corrected
You want to avoid overwriting specific fields in the target org
Controls how far the restore should go down the relationship tree from the selected top-level object (related lists / child records).
Restores only the top-level object records you selected.
Fastest and least intrusive option.
Restores the top-level records plus related records up to that depth.
Use when you need a predictable amount of related data.
Practical example
Restoring Accounts:
1 Level might include direct children like Contacts (depending on your schema)
2+ Levels starts pulling in grandchildren (e.g., Contact → Cases, etc.)
Restores the full related hierarchy (as far as the restore tool can traverse).
Use when you need completeness and are okay with a bigger restore job.
Gotcha: “All” can balloon the record count fast in complex orgs.
Lets you define a custom depth and/or relationship selection rules (implementation-specific).
Use when:
The numbered depth options are either too shallow or too broad
Controls whether Salesforce automation is disabled during the restore.
Leaves automation on (Flows, Workflows, Process Builder legacy stuff, Triggers, etc.).
Use when automation is part of the intended behavior and you want restored data to be processed normally.
Gotcha: Automation can modify restored values immediately, create additional records, or block changes with validations-so your “restored” state might not match the backup perfectly.
Attempts to disable Salesforce automation before restore and re-enable it after.
Use when you want the restore to be as “pure” as possible and avoid side effects.
Gotcha: Disabling automation can have org-wide impact while the job runs. Use with care, and ideally in lower environments unless you have a clear operational plan.
Lets you disable a specific subset of automation (implementation-specific).
Use when:
You want to minimize blast radius compared to “Disable All”
Click Save Changes after you complete required settings.
Next Step stays disabled until required fields are filled (Name, Restore Type, and Salesforce Org at minimum). Once saved, proceed to Scan Records.
Go back if you need to change the selected record set before committing configuration.
This stage is where the restore job actually writes data back into the target Salesforce org and shows live progress while it runs. Think of it as your “restore dashboard” – you can monitor overall progress, object-by-object outcomes, attachment handling, and basic container performance.
Continue Restore: continues the restore process (useful if the job was paused, interrupted, or needs to proceed to the next chunk of work).
Re-Scan Candidates: re-runs the candidate scan if you changed something upstream or want to re-evaluate what will be restored before continuing.
Cancel Restore: stops the restore process.
Next Step: go to View Results once you’re ready (typically after the restore finishes).
Previous Step: go back if you need to revisit prior configuration.
This is the “big picture” progress for the restore job.
What you’ll see:
A step indicator like “Step X of Y: …” (example shown: “Step 40 of 40: Restoring Attachment”)
A status message like Restore Completed
How to use it:
If progress is moving, the job is actively processing.
If it’s stuck on the same step for a long time, check Live Performance and the Completed Objects chart for heavy errors or bottlenecks.
Tracks attachment/file-type items separately from the main object record restore.
What you’ll see:
Counts like Uploaded and Skipped
Show Details link (bottom-right of the panel)
How to use it:
If you expected files/attachments to restore and see lots of Skipped, click Show Details and later review View Results to understand what was skipped and why.
It’s normal for attachments to be processed in their own phase (they’re often heavier and have different constraints than normal records).
A simple throughput graph showing how fast records are being uploaded over time.
How to use it:
Helpful for sanity-checking performance: if the rate drops to zero while the job isn’t complete, something may be blocked (errors, throttling, connectivity, etc.).
Small fluctuations are normal; huge flatlines usually mean the job isn’t currently uploading.
Quick view of container resource usage during the restore.
What you’ll see:
RAM Free (MB)
CPU Load (%)
Memory Usage (%)
How to use it:
If Memory Usage is very high and stays high, restores can slow down or become unstable.
High CPU during restore is expected; sustained maxed-out CPU + no upload progress is a red flag.
(This panel doesn’t fix anything by itself – it’s your “is my container dying?” gauge.)
This is the most useful panel for understanding what happened per object.
Legend:
Restored (blue)
Skipped (yellow)
Errors (red)
What it means:
Restored: records successfully written to Salesforce for that object.
Skipped: records intentionally not written (common causes: restore type settings, record already exists / doesn’t exist depending on insert vs update behavior, missing prerequisites, or other rules).
Errors: Salesforce rejected the operation or the restore job couldn’t complete it (permissions, validation rules, required fields, referential integrity, etc.).
How to use it:
A little yellow is often fine (especially for Update Only / Insert Only restores).
Red bars = you need to investigate. Move to View Results after the job finishes to see the error details and which records failed.
Click Continue Restore to run (or resume) the upload.
Watch Total Progress to confirm it’s moving.
Keep an eye on:
Completed Objects (especially any red “Errors” spikes)
When Total Progress shows Restore Completed, click Next Step to View Results and validate outcomes.
Skipped usually means the job decided not to write that record based on rules/settings. The two biggest drivers are:
Restore Type
Insert Only will skip anything it considers “already exists”
Update Only will skip anything it considers “does not exist”
Relationship/order constraints (child record can’t restore cleanly without its parent/state in the target org)
Use View Results for the exact per-record reason.
Attachments/files often have extra constraints (size, permissions, object support, target org state). Use Show Details in Attachment Progress, then View Results for specifics.
Finish the run (or stop if it’s exploding), then go to View Results and resolve based on the reported Salesforce errors (permissions, validations, missing required fields, etc.). After fixing the root cause, you can re-run a restore or adjust configuration and Re-Scan Candidates.
You’re restoring into a non-production org and want to exclude sensitive fields (depending on your org policies)
You need deep restore for one relationship branch, but not others
You know exactly which triggers/flows/validations are the problem
Upload Rate (should be non-zero while actively uploading)
