Date: Fri, 29 Mar 2024 05:51:56 +0000 (UTC)
Message-ID: <1156338934.69633.1711691516993@ip-10-0-1-26.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_69632_698079376.1711691516983"
------=_Part_69632_698079376.1711691516983
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Back up event databases
Back up event databases
Consider backing up the event databases frequently, depending on=
the volume of audit data you collect and your established disaster recover=
y strategies. For best results, use the following guidelines:
- Perform a full backup, including the transaction logs
- Schedule the backup during off-hours, or times when you expect the leas=
t audit activity
- Back up all event databases during the same backup procedure
- Save each database to a separate backup file
- Back up the SQLcompliance database during the same backup procedure to =
ensure audit data integrity remains intact
To back up the e=
vent databases:
- 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 =
to perform a full backup, including transaction logs, of the SQLcompliance =
database.
For each event database, perform a full backup, including the transaction =
logs. Each registered SQL Server instance has a corresponding event databas=
e. For more information, see Product components and architecture.
- Use SQL Server Enterprise Manager or Management Studio to bring the SQL=
compliance database online.
------=_Part_69632_698079376.1711691516983--