How to back up and restore the ePolicy Orchestrator database using SQL Server Management Studio
Last Modified: 2022-03-01 18:47:04 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
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.
How to back up and restore the ePolicy Orchestrator database using SQL Server Management Studio
Technical Articles ID:
KB52126
Last Modified: 2022-03-01 18:47:04 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x To identify what versions of SQL Server are supported, see: KB51569 - Supported platforms for ePolicy Orchestrator SummarySometimes Technical Support requires a backup of the ePO database. This article describes how to back up and restore the ePO database using SQL Server Management Studio.
See also a related article: KB67591 - How to run a SQL script provided by Technical Support against the ePolicy Orchestrator database Solution 1To back up an ePO database using SQL Server Management Studio:
NOTES:
Solution 2
To restore an ePO database using SQL Server Management Studio: NOTE: The steps in this article apply to all editions of SQL Server, including SQL Server Express, regardless of whether you use SQL Server Management Studio or SQL Server Management Studio Express. IMPORTANT: In ePO 5.10 and later, threat event information has been split into its own database, so it is required to restore both databases. Carry out the restore process on both the main database and the events database.
IMPORTANT: If you restore the ePO 5.10 events database, you must keep it the same original name because it is linked to the main ePO database by a synonym. When you restore the database by any other name than the original, that link is broken.
Related Information
See also the following Microsoft articles:
Previous Document ID (Secured)
614733
Affected ProductsLanguages:This article is available in the following languages: |
|