There are many ways of making SQL Server database backup, and there are as many methods as to how and where to store them. But is your method really convenient for you? Let’s assume that your backup plan is a full backup once a day, differential backup every six hours and transaction log backup every hour, and all these backups you need to send to OneDrive for Business. If you perform all the scenarios manually, it would take almost all of your time every day. Fortunately, you can do it in minutes with the help of SqlBak.
Backups
Recently we ran load tests against our SQL Server to see how server performance changes and how SQL Server responds to the load. If you’re interested here you can find a tutorial on how to simulate load against a database using free SQL Server load simulator How to Prevent Databases From Being Backed Up
There are cases when it is necessary to exclude one or more databases from a database’s backup list. If you administer a small number of databases you can do it simply by unchecking those databases which you don’t need to backup anymore. But what if you administer over 50 or even 100 databases? In this case excluding databases manually one by one is very inconvenient and time-consuming.
How to Group Several Notifications into One Email
Using SqlBak you can set email confirmation to get email notifications of successful or failed backup jobs. This is a very important part of your database backup strategy which will keep you informed in case if one of your backups failed.
On the other hand, sometimes notifications can be very annoying especially if you get several consequent errors within a short period of time. That’s why SqlBak has an option to merge several emails into a single one. Continue reading to see how it actually works.
How to Setup Failover Backup Storage
We would like to tell you about a brand new SqlBak feature that allows users to store backup files in a different place if the main destination fails.
How to manage multiple SQL backups in one place
Let’s assume that you have to administer over 100 databases that are stored on multiple servers. How can you make sure that every backup job is done as scheduled?
How often should I backup my database?
For almost any DBA, the question “How often should I backup my database?” is undoubtedly one of the most important to ask and answer. The answer, as with so many other questions in life, is “It depends”. Depends on what? Let’s discuss this.
How to Backup SQL Server Database to Amazon Glacier
Amazon Web Services (AWS) offers a large, sometimes bewildering array of server, storage, networking, and analytics cloud offerings, as seen here. One of their storage products is Amazon Glacier, in addition to the older storage solutions – S3 and Elastic Block Store (EBS). Glacier is a very affordable solution intended as a write-once, retrieve-seldom storage medium for long-term storage. Think of it as a storage locker that’s far away from your home, as opposed to your at-home garage or cabinet locker. It is also a good choice for your SQL Server backups …
Why Transaction Log backups are important
When backing up your SQL Server database, you have the option of taking transaction log backups. These are quick, small backups containing a sequence of all your database’s changes. Transaction log backups are mightily useful for point-in-time recovery.
Should You Back Up Your System Databases?
It goes without saying that as a DBA, one of your most important tasks is to schedule and ensure regular backups of your databases. But by ‘databases’ here, we usually mean your user-created databases. But SQL Server also automatically creates and maintains a number of system databases. So should you also back these up? Well, the answer isn’t a simple yes or no …