Questions regarding MSSQL backup
I have a customer who has a question regarding how Acronis handles MSSQL backups.
- Is it possible to backup the SQL log serparately at more frequent interval.
- The idea is to create a more frequent point-in-time recovery point.
- Only backup the full database once a day and backup the log every hour
- How does the log truncation work once the backup job is done. The customer would like to know more details on this process.
Thank you for any assistance.
thanks for posting on Acronis forums!
We recommend that you schedule incremental backups that could be run every hour and a full backup that runs once a day. Thus, your transaction logs are backed up hourly.
There is a Log truncation option . When it is enabled, the SQL transaction logs are truncated after each successful backup (i.e. every hour).
Good day Maria,
Thank you for you help on this matter. I appreciate your assistance answering my questions.
I would like to get some confirmation that it is not possible to backup the SQL log file separately, as in my original question? The recomendation is to run an incremental at the interval you wish to use to create a point in time backup.
With respect to my question on log truncation, I was looking for more details on the process run when the log truncation is performed. How are the logs truncated? Does the agent run a specific command or does it use a native MSSQL command?
Please bare in mind I am not a SQL expert.
Thank you again for your assistance.
I would like to get some confirmation that it is not possible to backup the SQL log file separately, as in my original question?
No, it is not possible to back up the SQL log as a separate object. However, if you select to back up your database every hour, this hourly incremental backup will contain this SQL log plus those data changes that have been performed during this hour.
How are the logs truncated?
A backup of an SQL database contains the database files (.mdf, .ndf), log files (.ldf), and other associated files. The files are backed with the help of the SQL Writer service. The service must be running at the time that the Volume Shadow Copy Service (VSS) requests a backup or recovery.
The SQL transaction logs are truncated after each successful backup.