Recommended procedure to migrate or move an ePolicy Orchestrator database to a new SQL Server
Last Modified: 2023-07-11 09:18:41 Etc/GMT
Prodotti interessati
Lingue:
Questo articolo è disponibile nelle seguenti lingue:
Découvrez comment un écosystème XDR qui s'adapte en permanence peut dynamiser votre entreprise.
Bryan Palma, PDG de Trellix, explique qu'une sécurité qui apprend et évolue en permanence est aujourd'hui indispensable.
Téléchargez le rapport Magic Quadrant de Gartner, qui évalue 18 fournisseurs selon des critères tels que la vision complète et la capacité de mise en œuvre.
Selon Gartner, « le XDR est une technologie émergente capable de renforcer l'efficacité de la prévention, de la détection et de la neutralisation des menaces ».
Quelles sont les cybermenaces dont les entreprises doivent se méfier en 2022?
Le secteur de la cybersécurité est en constante effervescence. N'attendez plus pour en tirer parti et dynamiser votre entreprise.
Deux leaders du marché de la cybersécurité unissent leurs forces pour créer un monde numérique résilient.
Bryan Palma, PDG de Trellix, explique qu'une sécurité qui apprend et évolue en permanence est aujourd'hui indispensable.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Recommended procedure to migrate or move an ePolicy Orchestrator database to a new SQL Server
Technical Articles ID:
KB68427
Last Modified: 2023-07-11 09:18:41 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x Microsoft SQL Servers - all supported versions For details of ePO- and SQL-supported environments, see KB51569 - Supported platforms for ePolicy Orchestrator. Summary
This article describes the recommended procedure to move the ePO database from one SQL Server to another. IMPORTANT : avant de commencer la procédure décrite dans cet article, sauvegardez impérativement votre serveur ePO. Pour en savoir plus, consultez les articles suivants de la base de connaissances : NOTES: The account used by ePO to access SQL must have the minimum needed permissions on the new server for ePO to function correctly. See KB75766 - SQL permissions needed to install and use ePolicy Orchestrator for details. IMPORTANT: In ePO 5.10 and later, threat event information is split into its own database. Carry out the actions on both the main database (default name Overview To move the ePO database, follow the steps below in the order that they're listed:
1 – Stop ePO services: Before you make any changes, you must stop ePO services to prevent anything from accessing the database:
McAfee ePolicy Orchestrator Event Parser McAfee ePolicy Orchestrator Server If you have any additional Agent Handlers, stop the following services on all Agent Handlers: McAfee ePolicy Orchestrator Server 2 – Move the database:
3 – Configure ePO and verify connectivity:
4 – Start ePO services:
5 – Extra steps for extra Agent Handlers: If you have more Agent Handlers, you must provide each one with the new SQL Server details by rerunning the initial setup wizard. Perform the following steps on each Agent Handler:
You can safely delete the database copy from the old server in the following scenarios:
6 – Optional: Remove service dependencies: IMPORTANT: You need to perform this step only if the ePO database was previously hosted on the ePO server itself. That is, the SQL Server was installed on the ePO server computer alongside ePO. If you moved the database from one remote SQL Server to another, you can safely ignore this step. If the ePO database was hosted on the ePO server, ePO services have dependencies on the SQL Server services. These dependencies mean that you're unable to stop the SQL services or uninstall SQL without affecting ePO. You must remove the dependencies from the services by editing the registry: ATTENTION : Cet article contient des informations sur l’ouverture ou la modification du Registre.
Prodotti interessatiLingue:Questo articolo è disponibile nelle seguenti lingue: |
|