If you use SqlBak to send backups to FTP Server, you can face a problem when though the connection seems to work, the file transfer doesn’t.
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.
We have updated the SqlBak Dashboard – this is the main control panel where users can see all of their backup jobs on a single page. The new features will be particularly useful for customers who have many DBMS backup jobs. Let’s take a look at how these new features can make your life easier.
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!