How to Run Incremental Refresh

After an environment is restored and users are ready to move over from the source environment to the destination environment, they can run MicroStrategy Backup Client to refresh the destination environment with any new changes made in the source environment.

Update mode updates the metadata, cubes, caches, images, plugins, Platform Analytics, and credentials in the following ways:

Metadata, Platform Analytics, and credentials
- Update mode updates the metadata and Platform Analytics warehouse from the backup file into the destination environment
- Credentials for the mstr, mstr_pa, and Administrator users in the project login, metadata database, and Platform Analytics warehouse are updated to the unified password, which is the password in the Welcome email of the destination environment
Cubes and caches
- Update mode removes existing cubes and caches, and restore cubes and caches from the backup file into the destination environment
Images and plugins
- Update mode restores images and plugins in the backup file into the destination environment, and will not overwrite the files with the same name

As the incremental refresh only updates metadatas, cubes, caches, images, plugins, and Platform Analytics, you can select those object types during backup for a faster refresh.

Go to the source environment and run the MSTRBAK client to create a backup. Refer to 3. Run MicroStrategy Backup.
If it is a clustered environment, then stop all other nodes except for a single node.
Go to the destination environment and install the MSTRBAK client. Refer to 2. Install MicroStrategy Backup.
On the destination environment and start a session using tmux. This prevents session terminations for a seamless restore.
Copy
```
tmux new -s <session_name> 
```
If the refresh process is terminated, it may lead to a corrupt metadata on the destination environment.
Run MSTRBak-Client in Update mode with the new backup files to refresh the destination environment.

For example, ./mstrbak -u https://s3.amazonaws.com/<bucket-name>/<file-name>.tar.gz.
The client runs and prints messages to the Terminal as it proceeds.
The execution is complete when the following message appears:
Copy
```
Successful MicroStrategy Refresh Execution for env-xxxxxx
```

Additional Flags

Append any of the following flags to the execution command as desired.

To show verbose logging, enter the parameter -v.
To receive email notifications about the backup process, enter the parameter -m <your email>.

For example,

Copy

./mstrbak -u <S3 URL> -m xxxx@microstrategy.com