Migrate to Visual-Guard 2024.X

Migration is a crucial process when upgrading to a newer version of Visual-Guard, a robust Identity and Access Management (IAM) solution. This process involves transferring all security configurations, user data, and settings from the old version to the new one. It requires careful planning and execution to ensure a smooth transition. It’s highly recommended to schedule sessions with Visual-Guard’s technical support team for guidance throughout the migration process.

Requirements

Before starting the migration process, ensure that your system meets the following requirements:

1. Download VG 2024.X: Download the VG 2024.X version by the respective link shared with you through the sales team.
2. DBA Attendance: Ensure that a Database Administrator (DBA)attends the migration session;

• Database-Level Permissions and Access Control: DBAs have the required database-level privileges to create, modify, and manage users, roles, and permissions, which may be necessary during configuration or troubleshooting.
• Data Integrity and Backup Planning: The DBA can review backup, recovery, and maintenance strategies to help prevent data loss and ensure system reliability.
• Efficient Troubleshooting and Support: Having a DBA present enables faster resolution of database-related questions and helps address potential issues early in the process.

3. VG Components Requirements:

You can check the requirements details from the below links.

Migration Steps

1. Backup: Before starting the migration process, please take a backup of all VG repository databases.
2. Uninstall: Uninstall all previous version’s components of Visual Guard in the machine where the new version’s components are being installed.
3. Environment Setup: Set up a parallel environment on a virtual machine and duplicate the environment. This allows you to run the Visual Guard in parallel environment and test before moving to the latest version. (Optional)
4. VG Installation: Install VG 2024.X in the new environment (VG Winconsole, VG Webconsole, VG identity Server).
5. Repository Addition: Add the existing repository that was created in the previous version.(Click here)
6. Migration and Licensing: Migrate to the existing repository and after successfully migrating, request for a new license. (Winconsole: Click here or Webconsole: Click here)
7. Upgrade VG Assemblies: Once the migration is done, upgrade each application to the required latest VG assemblies
8. Build Application: Once upgraded, build the application to make sure if everything is fine.
9. Generate VG Configuration File: Later, generate VG configuration file for each application from Win Console.
10. Decommission: Once the migration is done for all repositories and environments to the latest version and tested, upgrade all your application and decommission the previous versions. (Optional. This is required for parallel environments)
11. VG Components: Make sure all components of same version are installed i.e Winconsole, Identity Server & Webconsole.