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.
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 …
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.
A POS system backup is an essential task in any kind of business. Keeping your sales data safe for reporting and auditing is something all businesses should not cut corners in or treat with little importance.
When your company relies solely on an information system (database) to store all of its sales data, then it also must take all precautionary measures to protect this data and periodically make backups of the POS system’s database. We will show you how to do this in the article below.
If you’re looking for an easy way to quickly restore a database backup then you have found the right place.
Take a look at the article below to find out how you can achieve this.
Surely if you have arrived here you are facing this problem and looking for a solution. Well, you have come to the right place. In the article below we will show you how you can achieve this.
SqlBak’s dashboard has been upgraded to be a more user-intuitive interface, in order to provide the most essential information in just a quick glance as well as make modifications to the job.
It’s still very easy to create backups, to schedule them, to set custom backup destinations, and of course, all of the other features you will need to make sure your backup process is up to the highest standard. Let’s have a look!
If you can connect to your database, you can run this query and find out when was the last time your databases were backed up
and when were the last times a Full, Differential, or Transaction Log backup was taken.
But what do you do when you do not have remote access to your databases, but still like to have a quick review of your last successful backups? Well, we’ll cover this too…
Encountering a “Cannot perform a differential backup for database, because a current database backup does not exist” error might generate some confusion if you look into your backup log and can see that FULL backups have been successfully created.
This article will try to give you an answer as to why this happens and a solution, that will hopefully be applicable to your situation.