Offering a backup and disaster recovery service that works 110% of the time helps MSPs earn the trust and business of new and existing clients. Andrew Bensinger, CEO of Replibit, has more than 10 years of experience designing business continuity software. In this Expert Series webinar, join Andrew and Ted Hulsy, VP of Marketing at eFolder, as they discuss disaster recovery best practices that will help you meet and exceed the expectations of your clients.

1. 4. iSCSI Configurations
© 2015 eFolder, Inc. All Rights Reserved.1
Bad Good

2. BDR Do’s and Don’ts
Ted Hulsy
Vice President of Marketing, eFolder
ehulsy@efolder.net

3. Agenda
• Expert Introduction
• Building a Disaster Recovery Plan
• Having the Correct Hardware in Place
• eFolder BDR for Replibit
• Questions and Discussion
© 2015 eFolder, Inc. All Rights Reserved.3

4. Expert Introduction
© 2015 eFolder, Inc. All Rights Reserved.4

5. Building a Disaster Recovery Plan
1.Map Out the Live Environment
2.Define a Disaster Scenario
3.Build the Action Plan

6. 1. Map Out the Live Environment
Map out your client’s server and workstation
environment:
1. Find out the hardware specs of devices:
– CPUs
– Memory
– Storage
• Number of spindles/HD Type/ Raid Levels (underlying storage if VMs)
– SAS, SATA, SSD, iSCSI to NAS or SAN?
2. Define the roles of each server
– Are there any specialized applications installed?
© 2015 eFolder, Inc. All Rights Reserved.6

7. 2. Define a Disaster Scenario
• Disaster vs. Inconvenience
– How much downtime is needed before a disaster is declared?
• Help clients understand the implications of
declaring a disaster
– How long will it take to failback?
– Who does this cost? The client or MSP? Weekend work?
• Example 1: RAID controller fails and the hardware has a 4 hour
onsite warranty.
• Example 2: It is 4pm, the client’s office closes at 6pm and the client
just lost power.
© 2015 eFolder, Inc. All Rights Reserved.7

8. 3. Build the Action Plan
1. Determine the order that servers need to be
brought up in
2. Implement a method to test servers before
turning them over to clients
3. Calculate how long clients will be running in
emergency virtual mode
– Is the hardware under warranty or will the client need to
purchase new hardware?
– Will insurance cover this?
4. You now have implemented a P2V!
– Should you failback to bare metal or stay as VM?
© 2015 eFolder, Inc. All Rights Reserved.8

9. Having the Correct Hardware in Place
1.Minimum Requirements
2.Processor and Memory
3.Storage (local vs. iSCSI) and networking
4.Disk Types

10. 1. Minimum Backup Requirements
Backing up 1-5 protected systems (using Replibit):
• Processor: 4 cores
• Memory: 8 GB
• Storage:
– 1 dedicated local hard drive for the OS (250 GB min.)
– At least 1 additional drive for storing backup sets
For every additional 5 protected systems:
• Processor: an additional 2 cores
• Memory: an additional 4 GB
• Storage: additional storage as needed for backup sets
BootVM Check requires an additional 2 GB of memory and
2 processor cores on top of minimum backup requirements
© 2015 eFolder, Inc. All Rights Reserved.10

11. 2. Processor and Memory Notes
• Replibit utilizes the ZFS file system for the
storage pool containing the backup data. The
ZFS Project recommends ECC memory.
• Not all processors are created equal!
– Just because it is a Xeon processor, it does not mean it is hyper-
threaded. Verify the specifications of your processor. Ensure you
have the proper number of cores and GHz.
© 2015 eFolder, Inc. All Rights Reserved.11

12. 3. Storage Considerations
• Local storage is always preferred
• Use an HBA, RAID controller with JBOD mode
or the SATA ports on the mother board. Using a
hardware RAID card will make drive
replacement more difficult.
• If using iSCSI, 10Gbit Ethernet is required on an
isolated (VLAN or switch) storage network.
© 2015 eFolder, Inc. All Rights Reserved.12

13. 4. iSCSI Configurations
© 2015 eFolder, Inc. All Rights Reserved.13
Bad Good

14. Tid-Bits
1.Choosing Your Snapshot
2.Verifying the VM

15. ChoosingYour Snapshot
• Are you able to boot off a successful VM snapshot
taken at 2 AM, but are struggling to virtualize the
most recent snapshot?
– What was the reason for failure? Was it storage-related?
Remember: we are block level so there is a higher chance that
storage corruption is being ingested into the live backup.
© 2015 eFolder, Inc. All Rights Reserved.15

16. Verifying theVM
1. The very first boot in live mode should be to
Safe Mode
2. Once booted to Safe Mode, wait for Plug and
Play to run… and finish
3. After all the drivers have been installed
successfully, reboot.
4. The server will get a new address if DHCP is
available. Set your Static IP.
© 2015 eFolder, Inc. All Rights Reserved.16

17. Introducing eFolder BDR for Replibit
© 2015 eFolder, Inc. All Rights Reserved.17
An end-to-end backup and disaster recovery service that
bundles Replibit backup software, featuring chain-free
backup technology, and the massive cloud storage and
recovery capabilities of the eFolder Cloud

18. How it Works
© 2015 eFolder, Inc. All Rights Reserved.18
BDR Appliance
eFolder
Continuity Cloud
3. Emergency in-the-cloud
virtualization and recovery
Server
Agent
eFolder
Storage Cloud
Global Management Portal
Replibit Vault
Users
Disaster recovery options:
1. Download
2. Disk shipment
eFolder BDR for Replibit

19. Key Features
• Automated testing and screenshot verifications
– Daily screenshot of bootedVM
– Integrates with ConnectWise for automatic logging
© 2015 eFolder, Inc. All Rights Reserved.19

20. Key Features
Extensive data verification checks
• Every incremental is verified and no corrupted data is written to disk
• Incrementals are injected into aVirtual Hard Drive
• Nightly bootVM check and full block-level reconciliation in minutes
• No need for a RAID controller
• Tests include:
20
• BootVM snap
• Traverse the directory structure
• Numerate directories
• Read down master table for orphan objects
• Check for bad matching quadrants
• Review high fragmentation levels
• Real-time resilvering of data (coded ZFS)
• Block scans
• Sector scans
• TrackWindows Boot DLL files
• Agent disconnects
• Disk base utilizations
• Out of sync replication
• Lag on replication
© 2015 eFolder, Inc. All Rights Reserved.

21. Key Features
Deep ConnectWise integration
• Appliance andVault integration with full range of alerts
— Backup status, storage, utilization, replication, etc.
• Screenshot verifications of booted machine logged in tickets
• Customer agreement updates
• Tickets generated to the Service Board of choice
21 © 2015 eFolder, Inc. All Rights Reserved.

22. Key Features
Hardware-agnostic and OS-independent
• Linux Ubuntu hardened kernel can run on almost any server appliance
• No need for expensive Windows operating system components
• No reboot required after agent install
• Patching and updates happen automatically
22 © 2015 eFolder, Inc. All Rights Reserved.

23. Key Features
• Business-class:
– Powerful image-based backup software
– Chain-free backup technology (no dependent backup chains)
– Deep data verification and file system integrity checks
– Automated screenshot verifications of backups
– Free and fast pre-seed service
– Backups sent to the secure eFolder Cloud
– Encryption, with partner or user owned encryption keys
– On-site or cloud-based virtualization and recovery
• Flexible and reliable:
– Hardware-agnostic – Linux Ubuntu hardened kernel
– OS-independent –Windows server operating system not required
– eFolder supplied BDR appliances or build-your-own BDR options
– Recovery flexibility – P2V,V2P,V2V, P2P
– Multiple recovery options, including eFolder ContinuityCloud
• Channel-ready
– Multi-tenant model
– Partner branding
– Robust monitoring and alerting
© 2015 eFolder, Inc. All Right Reserved.23

24. Pricing
© 2015 eFolder, Inc. All Right Reserved.24
eFolder BDR for Replibit

25. Questions & Discussion

26. Thank you!
Ted Hulsy
Vice President of Marketing, eFolder
ehulsy@efolder.net