Date: Thu, 28 Mar 2024 22:32:34 +0000 (UTC)
Message-ID: <736855371.69447.1711665154533@ip-10-0-1-26.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_69446_1129466886.1711665154530"
------=_Part_69446_1129466886.1711665154530
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Restore the Repository databases
Restore the Repository databases
To recover lost or damaged audit data, restore the Repository da=
tabases. For best results, 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 Repository databases during the same restore procedure to e=
nsure audit data integrity remains intact
T=
o restore the Repository databases:
- Use the SQL Server client tools to close any open connections to the SQ=
Lcompliance database.
- Use the SQL Server client tools to take the SQLcompliance database offl=
ine. If you cannot take the SQLcompliance database offline=
, stop the Collection Service.
- Use a tool such as IDERA SQL Safe =
to restore the SQLcompliance database using the appropriate backup file, in=
cluding transaction logs.
- Use a tool such as IDERA SQL Safe =
to restore each event and archive database using the appropriate backup fil=
e, including the transaction logs. Each registered SQL Server instance has =
a corresponding event database. The number of archive databases depends on =
your archive preferences and your archive frequency.
- Use SQL Server client tools to bring the SQLcompliance database online.=
------=_Part_69446_1129466886.1711665154530--