Drobo Double Take

7/31/2019 Drobo Double Take

http://slidepdf.com/reader/full/drobo-double-take 1/15

Drobo How-To GuideConfigure Replication for DR Using Double-Take Availability and Drobo iSCSI SAN

drobo.com | Configure Replication for DR Using Double-Take Availability with Drobo iSCSI SAN 1

This document shows you how to use Drobo iSCSI SAN storage with Double-Take Availability to deliverreplication and DR for servers and applications. Double-Take Availability from Vision Solutions performsfour basic tasks:

• Mirroring. Transmittingdata, file attributes, andpermissions to the destinationserver

• Replication. Real-timebyte-level transmission offile changes

• Failover. Transferring ofservices to a stand-by serverin the event of a failure

• Restoration. Copying

replicated data, fileattributes, and permissionsfrom the destination serverback to the source

This guide covers the steps required to configure replication of user data between a production and stand-by server. For local replication, hosts can be attached to different volumes on the same Drobo. In an offsiteor high availability configuration, each host is connected to a separate Drobo.

What you will need & prerequisites Provisioning Drobo storage Installing Double-Take Availability softwareConfiguring Double-Take data replicationMigrating to a failover server Transferring services back to the primary server Restoring data

• Drobo iSCSI Storage, B1200i or B800i

• Drobo Dashboard management software

• Windows Servers 2003 or 2008 servers on current version at current patch level

• Vision Solutions Double-Take Availability installer and licenses

This document assumes that the Drobo iSCSI SAN has been deployed and Drobo Dashboard has beeninstalled. If the Drobo has not been configured, consult the Drobo Getting Started guide

• B1200i: http://www.drobo.com/media/pdf/Drobo_B1200i-getting-started.pdf

• B800i: http://www.drobo.com/media/pdf/B800i_GSG_Rev02_US.pdf





Start Drobo Dashboard andselect the Drobo to use toprovision storage.

From the Volumes menu onthe left side, choose AddVolume to launch thevolume creation wizard.

On the Format Typescreen, verify that theNTFS radio button isselected and click Next.





Using the slider, select avolume size that isappropriate for the data set.

Because Drobo is thinlyprovisioned, you canconfigure a volume greaterthan the size of the availablephysical storage. To avoidthe hassle of migrating datain the future, provision morestorage than is currentlyrequired.

Enter a name for the volumethat describes what it will beused for.

In this example, the volumeis named“DoubleTakeSource”, as itwill be the source data inthis replication scenario.

Click Finish. To create thedisk, click Apply.





The Drobo storage is nowavailable and ready to bemounted on the server.

Click the check box next tothe volume to attach thedisk.

When a checkmark appears,the disk has beensuccessfully mounted andthe drive letter is shown tothe left of the volume name.

To change the drive letter,

click the Rename Volumelink at the top right.

NOTE: Drive letters can bechanged only from withinDrobo Dashboard. Changesmade to drive letters at theOS level revert upon reboot.

Repeat steps 1 through 6 on the destination server. To simplify management, configure the storage tomirror the configuration on the source server. Standardizing drive letters, volume sizes, and clear namingconventions will ease management. In the example the destination volume is named“DoubleTakeDestination”.





Launch the Double-Takeinstaller and select Double-Take AVAILABILITY tobegin the installationprocess.

In the next few steps youwill be prompted to installpre-requisites and perform acheck for an updatedinstaller from the

manufacturer website.

It is highly recommendedthat you accept all updatesand prerequisitesautomatically applied by theinstaller.

Select Client and Server

Components to install theapplication and themanagement utilities.

Install the managementutilities on both servers, asthey will be needed in theevent of a system failure.





Enter the activation codeprovided by themanufacture for this

deployment and click Add.

Once the code has beenaccepted, click Next tocontinue.

Specify the amount of RAMto dedicate to the Double-Take application. While the

minimum requirement is512MB, it is recommendedthat you allocate at least1024MB of RAM.

Refer to the Double-Takesupport website for moreinformation on bestpractices for memoryallocation.

Click Next to continue.





In the event of insufficientnetwork bandwidth to

provide real-time replication,a disk queue will be used totemporarily store data.

Check the box to enable thedisk queue option and clickChange.

Browse to the Drobo storage,create a new folder named“DiskQueue”, and click OK.

Click Next to continue.

The firewall must beupdated to allow Double-Take to communicate withits replication partners.

Click OK to have the firewallrules automatically added.

NOTE: Even if the firewall isnot currently running on thehost, the automaticconfiguration option isrecommended.





Continue through theinstallation process until thewizard is completed.

The Double-Take applicationserver is now installed andready to be configured.

Repeat steps 1 through 7 on the destination server. Before replication can be configured, the Double-TakeAvailability application must be installed and running on both hosts.





Choose Start > Programs >Double-Take and load theDouble-Take Console.

From the Tasks menu,choose Add Servers.

Enter the hostname of theprimary server in the Server

box. Enter a valid user nameand password withadministrator permissionson the host, and click Add.

Repeat this step to add thedestination server, and clickOK to exit the wizard.





Click the Manage Servers icon at the top of theconsole and verify that both

hosts have been added.

If an error is displayed,delete the hosts and addthem again, verifying thatthe credentials entered arecorrect.

To configure replication,

click the Get Started iconat the top of the console.

Select Double-TakeAvailability and clickNext.

Select “Protect files andfolders or an entire server”and then click Next.





Select the source server andclick Next.

The source server is thereplication master that willhold the primary datasetthat will be mirrored to thedestination server.

To add directory exclusionsto the replication job, selectReplication Rules.

Select the path from thedirectory tree, and click AddRule to include or exclude apath.

Click on the ManageServers icon at the top ofthe console and verify thatboth hosts have been added.

If an error is displayed,delete the hosts and add

them again, verifying thatthe credentials entered arecorrect.





Select the destination serverfor the replication group and

click Next.

In a failover event the IP address of the primary server will be assigned to the destination server.

Uncheck all but the primaryIP address of the host andclick Next.

This page also presents theoption to modify otherproperties of the replicationjob. You can also configurethem later in the JobMonitor tab.

Verify that all items on thechecklist are met and clickFinish.

The replication set will becreated and replication willbegin immediately.





Click the Manage Jobs icon and select the job tofailover.

If the primary server isoffline the job will showa failed state.

Right-click the job andchoose Failover from

the menu to start thefailover wizard.

Select the Fail over

live data radio buttonand click Failover totransfer services to thesecondary server.

Once the failover job issubmitted, the IPaddress from theprimary server is

configured on thesecondary server and itappears on the networkas the primary server.





Click Manage Jobs andselect the job to bemanaged. Right-click thejob and choose Fallbackfrom the menu.

Click Failback to beginthe failover process.

The IP address of theprimary server will nowbe removed from thesecondary server.

Once the job has been transferred back to the primary server, a restore is required to synchronize all datathat was modified while the primary server was unavailable.





Click the ManageServers icon andselect the job to bemanaged.

Right-click the job andchoose Restore fromthe menu.

Select the server torestore data to andclick Continue.

All files that have beenmodified while theprimary host has beenunavailable will

synchronize to ensuredata is in sync beforereplication begins.

If the primary hostfailed and was rebuilt,all data will berestored.

When the restoration process has completed the servers are in sync and data mirroring can continue.

Drobo 2460 North First Street, Suite 100, San Jose, CA www.drobo.com 1.866.97.DROBO

Copyright 2012 Drobo, Inc. Data Robotics, Drobo, DroboEllite, DroboPro, BeyondRAID, and Smart Volumes are trademarks ofDrobo, Inc., which may be registered in some jurisdictions. All other trademarks used are owned by their respective owners.

All rights reserved. Specifications subject to change without notice. HT-0110-00 March 2012

Drobo Double Take

Documents

Transcript of Drobo Double Take