Appearance

Collect data ​

To realize migration, administrator must collect data of WALLIX Bastion:

  • Configuration data collected within back-up
  • Session recordings collected within session recording archive(s)

Where are WALLIX Bastion data? ​

Stand-alone deployment ​

Configuration data and session recordings are stored into stand-alone WALLIX Bastion.

Master-Master deployment ​

  • Same configuration data is stored in both master nodes.
  • Session recordings are distributed in both master nodes.

Master-Slave deployment ​

  • Configuration data is stored in master node.
  • Session recordings are distributed in all slave nodes.

How to generate the back-up? ​

IMPORTANT

WALLIX strongly recommends disabling all secret rotation workflows (scheduled rotation, check-in rotation, manual rotation) in the on-prem deployment to prevent any desynchronization during the migration.

Logged in GUI of the node with configuration data as a user with right Execute on feature Backup/restore. Generate a back-up on page System / Backup/restore:

Bastion back-up generation

NOTE

After back-up generation, any configuration added on the on-prem deployment cannot be migrated. Those configurations would have to be performed manually after the migration.

How to generate session recording archive(s)? ​

On each node with session recordings, logged in CLI as wabsuper, execute:

bash
/opt/wab/bin/WABSessionLogExport --start-date DATE --end-date DATE --passphrase BACKUPKEY -no-purge

DATE format is YYYY-MM-DD[HH:MM:SS]

NOTE

Use the same key to encrypt WALLIX Bastion back-up and all session recording archives.

NOTE

Recommended archive size is <4GB to ease data transfer and data migration. start-date and end-date parameters can be used to adapt size of the archives.