Date: Thu, 28 Mar 2024 21:45:25 +0000 (UTC) Message-ID: <496107929.69339.1711662325407@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69338_1980623814.1711662325406" ------=_Part_69338_1980623814.1711662325406 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A migration strategy moves the Collection Server components to a= nother SQL Server instance, thereby replacing the original Collection Serve= r. You can use a migration strategy to respond to an immediate maintenance = need. Use the following procedures and guidelines to implement a new migrat= ion strategy or modify an existing migration strategy.
When identifying the new SQL Server instance that will host the Collecti= on Server, ensure this instance meets or exceeds the product hardware, software, and permissions, as well as these specific requirements:<= /p>
Use a tool such as IDERA SQL Safe t= o perform a full backup of the Repository databases, including transaction = logs. You can back up event and archive databases separately from the SQLco= mpliance databases. However, for best results during a disaster recovery, f= ully restore all Repository databases at the same time.