Backups are a fundamental skill for most DBAs, and hopefully, for most technology professionals. For developers, I'd hope that most of you use some sort of version control, and that you back up your VCS database. I actually had someone ask why we needed to back up the VCS if we had the code on our machines. Certainly the local code on your system, or in your database, provides you some level of redundancy, but all the branches, all the code from other developers, you really want a real backup. For git, this is a simple file level backup.
I recently got a letter from Crashplan, who I've been using for a few years as a backup provider. Apparently they are exiting the home backup market, choosing to focus on businesses. I chose them since it was an economical provider, with good ratings, that let me back up multiple machines. I've been happy with them, tested a restores of a few files, but never needed the service. Now, I need a new solution. I keep two copies at home, but what about a fire or disaster? I want an offsite backup.
One of the things I've wanted with a backup solution is a hands off process. While I've managed to use cloud sync software and VCS reports to move most work stuff from one machine to others, there are pictures and other data that I don't want to lose. I've also got computers for my wife and kids that I'd like to have backed up. The Crashplan subscription for 5 computers worked great for me.
It doesn't seem there are a lot of providers out there for families. Most focus on businesses or the individual, which is fine. Backblaze seems like the next best choice, and at $50/yr/computer, perhaps that's a fair price. I've considered using Amazon Glacier and CloudBerry software, but that feels like I'm giving myself another management job to track. Though, maybe with PoSh available cross platform, I could just build a set of scripts to let each computer notify me if there are issues. I'm still trying to decide what makes sense.
Backup is important, and it's becoming a more cumbersome job over time. As my family generates more pictures and video, I get more concerned about backup. Especially the cost. The same problems and challenges I face as a DBA, though often with a slightly bigger budget. However, the challenge of balancing a budget with the requirements to meet some RPO is the same.
Fundamentals of SQL Server 2012 Replication provides a hands-on introduction to SQL Server replication. The book introduces you to the technologies that make up replication, and then walks you through setting up different replication scenarios. When you've finished reading, you should be able to implement your own multi-server replication setup while following the principle of least privilege. More »
The problem of ransomware seems to be increasing. Major organizations are being hit and their servers are being affected. K. Brian Kelley explains some of the basic things you can do to reduce your expose to ransomeware. More »
SQL Server T-SQL Recipes is an example-based guide to the Transact-SQL language that is at the core of SQL Server. This edition has been lightly updated for SQL Server 2014 and provides ready-to-implement solutions to common programming and database administration tasks. Learn to create databases, create in-memory tables and stored procedures, insert and update data, generate reports, secure your data, and more. Get your copy from Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
I want to create a large database in the year 2017, but I don't want to calculate a number of bytes. What are the options for the scale of numeric values in the MAXSIZE parameter? Meaning, as an example, can I use 10KB as a value instead of choosing 10240?
Answer: The KB, MB, GB, and TB abbreviations can be used.
As of now (2017), only the KB, MB, GB, and TB abbreviations can be used.
I was recently tasked with moving / ugrading SSIS packages from one server to another and I was instructed "to only move the packages that are executed by jobs".
This script joins three tables; sysjobs, sysjobsteps, and sysssispackages. It produces a list showing package name, job name, package folder name, and the job command. It is written for packages stored in msdb, but could easily be adapted for an SSIS package store. Additional columns could also be added.
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.