If you are upgrading a multi-node deployment, depending on whether you have a load balancer, you might be able to migrate servers to another OS without downtime.įor example, if you already had Deep Security Manager 9.5 on Windows 2003, to migrate the OS you would: If your server's operating system (OS) is not supported by Deep Security Manager 10.2, you must install a supported OS before you can install the manager. Migrate to a database type that's supported by both your current Deep Security Manager version and Deep Security 10.2. For databases supported by each version, see both the System requirements for this version and the install guide for older versions ( ).įor example, if you were currently using an Oracle 10g database with Deep Security Manager 9.5, you would migrate the database to Oracle 11g or 12c first (since it is supported by both Deep Security Manager 9.5 and 10.0), and then upgrade to Deep Security Manager 10.0.ĭeep Security Agents will continue with their current protection policies while the manager is stopped.īack up the database connection settings file: If you are upgrading Deep Security, to continue to store new data until you are ready to install Deep Security Manager 10.2, migrate to a database that is compatible with both current and future software. If the database is not compatible, you must migrate to a supported database before you can install Deep Security Manager 10.2. Before you install, all sections under Prepare your environment must be complete. The readiness check also customizes this guide for your environment's needs when you click View My Upgrade Guide. If you're not ready yet, you can cancel the install, and return when ready. The readiness check will generate a "to do" list of compatibility issues (if any) for your specific environment.įor example, you may need to free disk space, allocate more vRAM, or upgrade old Deep Security Agents to supported versions.
This will verify system requirements, and that all your deployment components are compatible with the new version of Deep Security Manager. Before it installs anything, it will check your environment. To verify software authenticity, compare the installer's hash with the vendor's published hash.Ĭheck compatibility: Start the installer. Compromised software can occur with an insecure, plain HTTP connection or download from third parties.
Verify that installers are authentic, not modified.
0 kommentar(er)
