Downgrading v3.x
- Downgrading within v3.x
- Downgrading from v3.x to v2.x
- Restarting containers
- Appendix: Migration reference
Downgrading within v3.x
Note: These instructions are for DataMasque installed in a Docker or Podman environment. For specific instructions for downgrading on EKS or Cohesity, please contact support@datamasque.com.
It is not necessary to stop the DataMasque containers before downgrading these versions. To reach older versions, downgrade step-by-step through each version.
First, find your current version in the table below:
| Current Version | Migration Command | Target Version |
|---|---|---|
| v3.26.06 | None required (skip step 2) | v3.26.05 |
| v3.26.05 | migrate masque_entities 0119 then migrate file_masking 0003 |
v3.26.04 |
| v3.26.04 | None required (skip step 2) | v3.26.03 |
| v3.26.03 | migrate masque_entities 0118 |
v3.26.02 |
| v3.26.02 | None required (skip step 2) | v3.26.01 |
To downgrade multiple versions: Run each migration command from the table in sequence (top to bottom), skipping any None required entries. Then install your final target version.
Then follow these steps:
Back up rulesets, connections, and seed files.
Undo migrations using the command from the table above:
# Docker
$ sudo docker exec -it datamasque_admin-server_1 bash django_manage.sh <MIGRATION_COMMAND>
# Podman
$ sudo podman exec -it datamasque_admin-server_1 bash django_manage.sh <MIGRATION_COMMAND>
- Install the target version:
$ tar -xvzf datamasque-v<TARGET_VERSION>.pkg
$ cd datamasque/v<TARGET_VERSION>/
$ sudo ./install.sh --upgrade --force # add --podman for Podman
- DataMasque should start within 5 minutes. If not, see Restarting containers.
Downgrading from v3.x to v2.x
Downgrading from DataMasque v3.x to any v2.x version is not supported. v3.x includes significant infrastructure changes that prevent reverting to a v2.x installation.
If you need to return to a v2.x version, you will need to restore from a backup taken prior to upgrading.
For further assistance, please contact the DataMasque support team at support@datamasque.com.
Restarting containers
If DataMasque doesn't start within 5 minutes, try forcing the containers to restart.
Note that these instructions assume DataMasque is installed in the default directory /usr/local/etc/datamasque. If you specified a different path during installation, update the path accordingly.
# Docker
$ sudo docker compose -f /usr/local/etc/datamasque/docker-compose.yml restart
# Podman
$ sudo docker-compose -f /usr/local/etc/datamasque/docker-compose.yml restart
Appendix: Migration reference
For advanced users or support reference, here are the database migrations that changed between versions:
| Version | Migration App | Migration Target |
|---|---|---|
| v3.26.06 | None | N/A |
| v3.26.05 | masqueentities + filemasking | 0119 + 0003 |
| v3.26.04 | None | N/A |
| v3.26.03 | masque_entities | 0118 |
| v3.26.02 | None | N/A |