Prerequisites to upgrade from DLP Beta to GA release

Products

• Data Loss Prevention
• Data Loss Prevention Enforce

Issue/Introduction

This article serves as your comprehensive guide to upgrading from DLP Beta to the General Availability (GA) release.

Resolution

Please find below the steps to upgrade from DLP Beta to GA release:

1. Upgrading from a Symantec Data Loss Prevention (DLP) Beta release to a General Availability (GA) release requires specific procedures to ensure database readiness and server connectivity.

2. Database Readiness (URT):
- Before upgrading, you must run the Update Readiness Tool (URT) to verify the database schema. When upgrading from a Beta release (e.g., 25.1 Beta), the URT will likely fail with multiple errors related to missing tables, columns, and indexes because it defaults to validating against the GA schema.

Action: Execute the URT with the mandatory --beta parameter. This informs the tool to validate the existing Beta schema correctly.
Command Example: "<Install Drive>\Program Files\AdoptOpenJRE\bin\java" UpdateReadinessTool --beta

Refer this link for more information.


3. Upgrade Sequence and Connectivity:

To maintain connectivity between servers during a Beta-to-GA upgrade:

- Order of Operations: Upgrade all Detection Servers(on-premise servers only) to the GA version first, then immediately upgrade the Enforce Server to the same GA release. Check this link for more details.
- UDS Errors: If you encounter SEVERE: Severe error for application connection [connectionType=UDS] after upgrading from 25.1 Beta to GA, verify the keystore files. You may need to copy the monitor..jks file from the Enforce server's keystore directory to each detection server's keystore directory and restart services.

4. In addition to the steps above, please follow the general documented DLP upgrade procedure.