|
Didn't notice there was a Backup thread, so I had originally posted this in the Ticket Came in thread.... Anyways... Anyone have any recommendations for a proper and safe way to backup MS SQL databases off-site/to the cloud? We have 3 Server 2008 R2 SQL databases, about 67GB in size total. Each database sees 2-5GB of changes per day. Right now we take log backups every hour, and a full backup every night that are stored on removable disks (RDX-like disk cartridges). The full .BAK files as generated by SQL Server are 56GB currently. My problem is that the sending site has a 10Mbit upload, and only a 6 hour window in which it could be fully utilized. So uploading the .BAK files nightly definitely out of the question. Does anything exist out there that can perform a safe, off-site backup while only transferring changes/deltas? From what I can find, the general consensus is that the only safe SQL backup is the one generated natively by SQL Server. But .BAK files seem to have so many changes from day to day that it renders delta based solutions (like rsync for example) useless; they end up transferring nearly the entire file again.
|
#
¿
Apr 2, 2015 17:16
|
|
|
|
| # ¿ May 2, 2024 18:01 |
|
|
ConfusedUs posted:The "general consensus" you speak of is a very old school of thought. Sure, 12 years ago, when VSS was new, third-party backup stuff sucked. Today? Nah. There's a dozen applications that can do this for you. I kinda figured it that, but really couldn't find much to support it. I am not a DBA by any means. Just the lowly computer janitor responsible for making sure it gets backed up. quote:Carbonite Server Backup can do your MSSQL databases (and all sorts of other things), and is the one I'm most familiar with. I'll look into it definitely. Was already looking at Carbonite anyways to backup workstations at some of our branch locations... quote:The only real gotcha here is that MSSQL itself has a limitation where it doesn't keep track of what is backing it up; only that a backup occurs. If you throw multiple applications at the same database, it'll break your inc/diff backups for one or both until that application performs its next full backup. This is true for any application, but some people don't realize this, and then get pissed when they try to run both during a trial phase. Hmm... well crap. I definitely want to continue to do the local physical backup. But add the online backup as a backup to the backup...
|
|
#
¿
Apr 2, 2015 18:55
|
|