
As for the backup strategy, a typical backup scheme might include weekly full database backups, daily differential backups, and frequent intervals of the transaction log (INCR) backup, e.g., every 15 minutes. SEP recommends using the full recovery model.

Full backup: A full database backup backs up the entire database stored on the MS SQL server, including the transaction log.SEP sesam supports the following SQL Server backup levels: For details, see Listing SQL Servers from the command line. The names of the instances and databases can be retrieved using SQL Server Management Studio. If the database belongs to a SQL Server instance, the server and instance must be explicitly specified: //. The source for a MS SQL Server backup must contain the SQL Server database name. The supported backup levels depend on the selected recovery model, as described in the section Selecting a recovery model for your MS SQL database. The SEP sesam database module for MS SQL is part of the Client package and enables the backup of one or more MS SQL databases (the feature to backup multiple databases is deprecated in Apollon release, see below). If you are using an older SEP sesam version, refer to Documentation archive.

Visit SEP sesam YouTube Channel for latest videos and webinars.Ĭheck FAQ to find the answers to most common questions. Support for MS SQL AlwaysOn Availability Groups.
