Feed your Appetite for Reduction. Meet us at booth #605 at AWS re:Invent.
Microsoft SQL Server is a long-standing gold standard in relational databases, even for cloud applications. But organizations that have migrated their SQL Server to the cloud are probably realizing that Native SQL Server Backup is better suited to its traditional on-premises deployment than the modern cloud-hosted instances. This blog explores how native SQL Server backups work, where they fall short, and how Clumio compares.
Native SQL Server backups are the built-in backup mechanisms that allow users to create backups of databases and transaction logs directly from within SQL Server. Since these built-in backup methods apply across versions and hosts, they are very popular.
SQL Server’s native backup scheme involves multiple different types of backups. To understand how the backups work, we must first understand SQL Server’s recovery models. These are database properties that control how transactions are logged, whether the transaction log requires and allows backups, and the available restore options.
SQL Server has three Recovery models: Simple, Full, and Bulk Logged. Users must select one for each SQL Server database, but it can be changed anytime.
Equipped with an understanding of recovery models, we can now explore how they interact with the different types of SQL Server-native backups, and what this means for database backup and recovery.
Clumio is a simple, automated solution for backing up your SQL Server on Amazon EC2. Air-gapped and immutable by design, Clumio helps organizations recover instantly from ransomware and operational disruptions, automate data retention and compliance, and optimize storage costs.
Clumio for SQL Server on EC2 reduces performance impact because it takes incremental backups. These differ from differential backups in that after one initial full backup, they continue building upon one another forever, making them faster and lighter weight. This additionally means that when restoring the database, there is no need to separately restore full and differential backups and roll back transaction logs–everything is restored together as one full backup. Clumio can also be set to take backups from the secondary replica in your Always On Availability Group, completely removing any performance impact on the primary database.
With Clumio, you can set when and how often incremental, database-level backups are taken, and how long they’re retained. You can set the frequency with which your transaction logs are backed up, down to every 15 minutes, and you can choose whether to have your backups taken from a replica in your Always On Availability Group. Once these choices have been made, your backup plan is automated, requiring no ongoing maintenance.
Here we explore Native SQL Server backups’ functional challenges and Clumio’s advantages:
Many native SQL Server backup challenges stem from the fact that they have to be scripted and managed by the user. Here we compare these to Clumio’s benefits:
While you could backup your SQL Server on EC2 using native SQL Server backups, there’s a better strategy for backing up SQL Server databases on Amazon EC2. Clumio is a simpler, more secure, and more performant backup and data recovery option. Learn more about Clumio for SQL Server on EC2 on the product page, or download The Essential Guide to backing up SQL Server DBs running in AWS.