Protect Your Customers|
Healthy Server Reseller News |
Feb 23rd, 2009 |
||
In this issue
|
Service For
Your Customer |
||
|
GFS Incrementals vs. Block-Level Full Backups In the beginning, there were only full data backups, which replicated the entire system completely from start to finish. Full backups were a pretty good solution at the time, when data storage needs were minimal and most of the world still operated on paper. But flash forward a few years and the amount of data needing regular backups skyrocketed, making full backups time-consuming to the point that they began interfering with business operations and taking up too much space. With this exponential increase in data volume, a new solution was needed on the scene to speed up the backup process and use backup space more efficiently. Enter the "incremental" solution, which parses only server files ("increments") that have changed since the previous backup. It certainly solves the backup time problem—what took many hours now takes only a mere fraction of the time. But while it speeds up the backup process, it also introduces significant complexity and risk for human error. Part of the reason is the complex scheduling required by incremental backups. There are three types of rotating backups required—grandfather (monthly), father (weekly), and son (daily)—and all of these increments are backed up to tape. If the server crashes, restoring becomes a complex chore of loading the master tape, then all changes made to the server since that are contained on multiple tapes. And if the time-consuming restore process isn't tedious enough, if any tapes are corrupted anywhere in the chain, the server cannot not be fully restored. So what's the solution? Getting the best of both worlds with full offsite backups made possible by block-level, differenced changes. Offsite block-level full backups save time and space during backups and make for easy system restores because the entire system has been backed up in one location. Imagine a server crash that can be restored in a few clicks of a mouse, instead of hunting down tapes and hoping that they'll work. Similar to incremental backups, only files that have been changed from the previous day are backed up, but by using a differential backup method to an offsite server—the most advanced method to date—the backup is automated, more precise and requires less time and space. Best of all, it is a full backup, which means that system restores are just as easy to execute as full backups. CncOp™ (pronounced sink-up) is Carroll-Net's offsite block-level full backup differencing engine that performs a full backup each night and houses it in the secure Carroll-Net Datacenter. Find out more about how CncOp can backup your customer's data effortlessly at: http://www.carroll.net |
If you're in the Livingston, NJ area we'd love for you to stop in and see us at our booth. The conference is from 8am - 3pm and includes breakfast and lunch. The topics are Cloud Computing and Virtualization. Carroll-Net has a limited number of FREE passes. Call today to reserve yours (888)432-1638 |
||
|
CncOp's Block-Level Full Backups When your customers trust their data backups to Carroll-Net's (CNet) Healthy Server™, they're getting the best aspects of incremental and full backups in one complete block-level full backup system. Built on CNet's patent-pending CncOp™ technology, backups are effortless and full restores take mere minutes instead of hours or days, and there's no tape required. CncOp is a differencing engine that performs full offsite backup each night by sending only block-level changes over your customer's Internet to the Carroll-Net Datacenter, where these changes are re-played to the backup set, automatically creating a full backup that is instantly accessible. Once your customers experience how reliable and quick and easy full backups (and system restores!) can be, they'll thank you for rescuing them from hours of maintenance backups and tape-stack troubleshooting. Find out more about CncOp at: http://www.carroll.net |
Copyright (c) Carroll-Net, Inc., 2009
If you wish to cancel your subscription to this newsletter, click here