building and configuring a storagecraft bdr

The decision has been made.

At this point, you’ve decided whether to build or buy and determined that building your own backup and

disaster recovery (BDR) appliance is the right option. Building a BDR will give you more scalability and flexibility, however, the BDR must be built correctly in order to have a successful disaster recovery (DR) solution. Important to note is that a BDR may require different resources based on the network environment in which you are using it. In this guide, we’ll walk you through the considerations you need to make when building a StorageCraft-powered BDR.

What a good BDR does Before we start, let’s think about what a good BDR appliance is capable of. A BDR can be a key component in a successful DR solution. DR differs slightly from

simple backup in that instead of just taking and storing backups, you give yourself quick recovery options like local or cloud-based virtual failover. A true BDR is designed to be used as a failover platform for any networked system that goes down. It will not only let you store StorageCraft® ShadowProtect® or StorageCraft ShadowProtect SPX backup images, but will also allow you to replicate them offsite using StorageCraft ImageManager™, and even virtualize backups with StorageCraft VirtualBoot™ for near-instant recovery. Failover options like local or cloud-based virtualization let businesses greatly reduce costly downtime and create solid recovery time objectives (RTO; see About Recovery Objectives). Your BDR will have all of this storage and failover functionality inside one easy-to-use appliance that makes reliable failover simple and quick.

Building and Configuring a StorageCraft BDRA guide by StorageCraft Professional Services

Considerations for your BDR

Hardware quality is essential when building a BDR. A BDR might be your only lifeline when a failure happens, and if it goes down while it’s being used for failover, the results could be devastating. For that reason, we suggest using new, quality equipment (not used or refurbished) that’s also protected with redundant features like RAID, redundant power and fans, and so forth. Ideally, your equipment should also be under warranty.

For a BDR to be a successful failover platform, you will need to build and configure it correctly. If at any point in this guide you have trouble building your BDR or have questions about implementation, our Professional Services team can give you the quick help you need (see About Professional Services).

In order to illustrate how you’ll build your BDR, we’ll use a scenario for the fictional “ACME Company.” In this example (see Figure 1), ACME has four servers: A Microsoft Exchange server, a file server, a web server, and domain controller, along with multiple desktop user systems. Each of these servers and desktops will be backing up data to the BDR appliance.

The following are a few areas to consider when building a BDR for a successful DR solution:

• Processor • RAM • Storage space • Disk configuration • OS • Virtualization • StorageCraft components • Management • Location • Off-site strategy

Processor The processor for the BDR needs to be powerful enough to handle any running virtual machines (VMs) for servers that have failed in production and been recovered from the last backup image using VirtualBoot. For example, using the ACME scenario, if the file server fails, the BDR needs sufficient processing and cores to handle the VirtualBox VM for the recovered file server and the other functions handled by the BDR (OS, ShadowProtect, ShadowControl, ImageManager, etc.).

RAM The BDR needs to be configured with sufficient RAM to handle regular daily functions (OS, ShadowProtect, ShadowControl, ImageManager, etc.) in addition to the RAM needed to support any potentially running VMs you might use for recovery. When building a BDR, it’s best to consider how many systems would be recovered to VMs in a worst case scenario. In the ACME scenario, the RAM used by the servers is as follows:

• Domain Controller – 8 GB • File Server – 8 GB • MS Exchange – 24 GB • Web server – 16 GB

Figure 1

BDR LOCAL SITE

OFFSITEBDR

INTERNET

SERVERS DESKTOPS

Building and Configuring a StorageCraft BDR

Now let’s look at a couple of examples. If the file server crashes, the BDR would need approximately 4 GB of RAM for daily functions and 8 GB of RAM to support the recovered file server VM for a total of 12 GB (see Figure 2).

But what if both the file server and the MS Exchange server crash? In that case, the BDR would need 4 GB for daily functions, plus 8 GB for the file server, plus 24 GB for MS Exchange, for a total of 36 GB (see Figure 3).

Now what if all of the servers went down in a server room fire or flood? The BDR would need enough resources to be able to support all four servers in recovered VMs.

Storage Space

The BDR is a repository for backup images from all systems being backed up. You will need enough space to hold the full backup image for each system, plus all of the incremental images stored for retention. StorageCraft backup images are compressed at 40%, on average, which will save on space. ImageManager will also consolidate images and delete old images based on the retention policy you have chosen. All of these factors need to be taken into consideration when building the storage for your BDR to ensure you have the space needed for new images over the next 1-2 years, or however long you deem necessary.

Selling Disaster Recovery as a Service

A BDR appliance is just one of the ways an IT service provider can sell disaster recovery as a service (DRaaS). Not all businesses can afford a BDR, but no business can go without a backup and recovery plan. Read our guide Selling Disaster Recovery as a Service to learn a number of ways you can sell effective backup and DR services to clients with any kind of budget. You’ll also learn how backup and recovery is not only an essential concept for every business, but how it’s also a revenue-generating opportunity for any service provider.

FILE SERVER VM

SHADOWPROTECT SPXIMAGEMANAGER

SHADOWCONTROL

VirtualBox

Windows

(In Gigabytes)

8TOTAL

412

Figure 2

TOTAL

VirtualBox

FILE SERVER VM EXCHANGE VM

24

SHADOWPROTECT SPXIMAGEMANAGER

SHADOWCONTROL

Windows

4

8

(In Gigabytes)

36

Figure 3


Disk Configuration

Correct disk configuration is critical. In the event of a system(s) failover, the BDR will be running a hypervisor and VM(s), an OS, and StorageCraft management software (ImageManager, ShadowControl). If there is just one drive, or RAID5, this will cause a bottleneck on I/O and recovered servers (VMs) will not perform well. To alleviate this, the disk configuration should be C: for the OS, and D: for the backup image data. Both of these can be on a RAID5. The VM’s should be stored on a separate disk (V:) or RAID1/RAID10 (not a part of the same array as the system and data volumes) to allow for better performance during failover (see Figures 4 and 5).

Using solid-state or other high-performance drives in your BDR will improve performance of any failover machine. During the VirtualBox installation, change the Default Machine Folder to this separate drive\controller.

Operating System

We recommend using an up-to-date, server-class operating system on your BDR. Windows client operating systems have connection limitations, which may end in undesirable results. If the BDR is owned by the solution provider, a Microsoft Service Provider Licensing Agreement (SPLA) may be an option. Another option is providing an OEM license which can be obtained by providers such as Avnet®.

Linux-based operating systems may be an option, as long as it’s a supported distribution of StorageCraft SPX (see our supported Linux kernel versions). ImageManager, however, is not currently supported on Linux, so provisions must be made to operate ImageManager from one of the less-utilized Windows servers.

If the BDR needs to perform recovery of both Windows and Linux operating systems, the BDR will need to use a Linux distribution that supports SPX for Linux.

Virtualization

To function as a failover platform, the BDR has to have a hypervisor installed. To utilize StorageCraft VirtualBoot you will need to install the version of VirtualBox that is supported by the version of ShadowProtect/SPX you are running on your BDR (see our supported versions). Note that a supported Linux distribution can Virtualboot Linux or Windows operating systems, but a Windows BDR can only Virtualboot Windows operating systems.

StorageCraft Components

Optimally, the BDR will have installed the Mount Services (if utilizing ShadowProtect 4.x/5.x) or an unlicensed version of SPX (if utilizing SPX). If the BDR has a Windows OS, then the BDR is the best location for ImageManager. Finally, we recommend installing the StorageCraft ShadowControl™ Endpoint Agent if using ShadowControl for monitoring and/or management.

Management

The BDR is a central point for management of StorageCraft backup images. This is where ImageManager is installed to manage the folders for all systems (unless the BDR is installed on a Linux distribution, then ImageManager needs to be installed on a Windows OS—whichever server has the most available resources).

RAID 5 ARRAY

RAID 5 ARRAY

RAID 1 ARRAY

Figure 4

Figure 5


Location

A BDR could be racked in the server room with the other servers, but we recommend moving it to secondary location. In the event of a catastrophic event like a fire or flood in the server room alone, all systems including the BDR would be offline. This can be devastating to a company because all of the employee systems and personnel will be functional but servers and data will not. In this situation, recovery would need to happen from off-site data, which may be time consuming, if the data was even stored offsite to begin with.

Placing the BDR away from the server room provides separation. If the server room has a fire, flood, or other issue, the BDR will be safe in another part of the building and can be used to quickly VirtualBoot the failed servers to get the company’s personnel and operations back online and productive.

Off-Site Strategy

In the event of a site-limiting or site-destroying event, having a defined off-site strategy is critical. The best practice is to have the BDR replicate to StorageCraft Cloud Services™ at the premium service level. This will allow you to recover all backed up systems in the StorageCraft Cloud using the pre-staged networking and configuration, which accelerates your ability to use the lost systems. Alternatively, it may be acceptable to configure the BDR to replicate to another BDR or off-site location to perform the restoration process from a secondary site. This may limit your recovery time objective, but will at least keep data safe in another location.

Summary

From here, you should have the information you need to start building your BDR appliance. If you run into trouble, our Professional Services Team can help you with the BDR itself, or even if you need assistance on a client rollout or guidance on anything in the area of backup and disaster recovery. If you’re curious how a lot of StorageCraft partners make money selling BDR appliances, check out our guide Selling a BDR Appliance.

While this document outlines the considerations needed to build a BDR, there are several “off the shelf ” devices from StorageCraft Alliance Partners that fit in a variety of business environments and can assist with various disaster recovery needs. In addition, look for further white papers from StorageCraft that outline sample BDR configurations from major hardware vendors.


About Recovery Objectives

When you’re trying to understand tolerance to downtime, there are two things you’ll really want to know:

• How long can you or a client be without a certain piece of equipment?

• How much data can you or a client afford to lose?

The answer to these two questions will help determine the two most important numbers for backup and disaster recovery planning: recovery time objectives and recovery point objectives.

A recovery time objective, or RTO, is most useful in helping you understand the kind of recovery strategies and technologies you need in place to successfully recover from a disaster. Put simply, RTO is a measurement of your client’s tolerance for downtime. Once you know what that tolerance is, you’re in a better position to plan the recovery. Note that RTO is not really useful in helping you recover data or set up backup schedules. Instead, it prepares you to get your systems up and running before clients start hemorrhaging money, reputation, and so on. For a more detailed guide on determining RTOs with clients, read “What is RTO?”

A recovery point objective, or RPO, is the other metric you need to discuss with clients. RPO is a useful tool when it comes to planning and executing backups. At its most basic, an RPO is a measurement of tolerance for data loss and it can help you and your clients decide how often they need to be backing up, as well as what sort of infrastructure you need in place in order to support those backups. Keep in mind that, despite its

name, an RPO has less to do with the actual execution of a recovery than it does with helping you lay the groundwork, so when you do have to recover, you’ll recover everything you need. For more information on RPOs and how to determine them, read “What is RPO?”

About StorageCraft Professional Services

StorageCraft® Professional Services is our expert team of backup and disaster recovery professionals who provide design and implementation services as well as quick assistance to StorageCraft partners. Our Professional Services team goes way beyond break-fix support and product education to provide you with focused consultation services.

If you want a specialist to implement a disaster recovery solution for your customers, or if you need an expert to review a disaster recovery plan you’ve created, you can rely on StorageCraft Professional Services.

Contact them at [email protected].


Brett Twiggs, Director of Professional ServicesBrett has more than 20 years of experience working in the IT industry, including many technical and senior management roles. Before StorageCraft, he was a technical account manager with AccessData, where he provided forensic and legal eDiscovery services for Fortune 100 clients. He has also worked at LANDesk, DirectPointe, Critical Network, and The Walt Disney Company, where he was a senior network analyst. Brett has a bachelor’s of science in economics from Brigham Young University and an executive MBA from the University of Utah.

Author

StorageCraft Technology Corporation380 Data Drive, Suite 300

Draper, Utah 84020 www.StorageCraft.com

[email protected]

Copyright ©2015 StorageCraft Technology Corporation. All rights reserved. This publication is for informational purposes only. STORAGECRAFT MAKES NO WARRANTIES, EXPRESSED OR IMPLIED, IN THIS PUBLICATION. StorageCraft is a registered trademark and Recover-Ability is a trademark of StorageCraft Technology Corporation. All other brands and product names are trademarks or registered trademarks of their respective owners.

building and configuring a storagecraft bdr

Documents