Date: Thu, 28 Mar 2024 16:04:45 +0000 (UTC)
Message-ID: <213019955.68081.1711641885244@ip-10-0-1-26.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_68080_1951516894.1711641885234"
------=_Part_68080_1951516894.1711641885234
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Restore event databases
Restore event databases
Restore the event databases to recover lost or damaged audit dat=
a, according to your established disaster recovery strategies. For best res=
ults, use the following guidelines:
- Perform a full restore, including the transaction logs
- Schedule the restore during off-hours, or times when you expect the lea=
st audit activity
- Restore all event databases during the same restore procedure
- Restore the SQLcompliance database during the same restore procedure to=
ensure audit data integrity remains intact
To restore the=
event databases:
- Use SQL Server Enterprise Manager or Management Studio to close any ope=
n connections to the SQLcompliance database.
- Use SQL Server Enterprise Manager or Management Studio to take the SQLc=
ompliance database offline. If you cannot take the SQLcomplian=
ce database offline, stop the Collection Service.
- Use a tool such as IDERA SQL Safe&=
nbsp;to restore the SQLcompliance database using the appropriate backup fil=
e, including transaction logs.
- Use a tool such as IDERA SQL Safe&=
nbsp;to restore each event database using the appropriate backup file, incl=
uding the transaction logs. Each registered SQL Server instance has a corre=
sponding event database. For more information, see Product components and architecture<=
/a>.
- Use SQL Server Enterprise Manager or Management Studio to bring the SQL=
compliance database online.
------=_Part_68080_1951516894.1711641885234--