TechTarget Backup School New Customer Training | 1 2014 ExaGrid Systems, Inc. Confidential Backup...

TechTarget Backup SchoolTechTarget Backup SchoolNew Customer Training

exagrid.com | 1 © 2014 ExaGrid Systems, Inc. Confidential

Backup School

www.exagrid.com

Backup School

www.exagrid.com

New Customer Training

www.exagrid.com

WELCOME TO EXAGRID



Agenda

High Level Architecture Overview • Deduplication

Discuss Scope of Share

Data Processing Overview • Deduplication & Delete

Alerting

exagrid.com | 2



Backup 5

10TB

5TB

10TB

5TB

10TB

5TB

10TB

5TB5TB

Advanced Architecture for Instant Recovery

Backup 1

Landing Zone

Repository2:1 Compression

High speed landing zone.Most recent backup in complete form for Instant VM Recovery

Backup 2

Byte-level deltas of compressed zones

Backup 3 Backup 4

200GB200GB 200GB 200GB 90TB backed up to 6.6TB

repository space

Backup 1

Backup 2

Backup 3

Backup 4

Backup 5

6.6TB

Backup 6

Backup 7

Backup 8

Backup 9

200GB200GB 200GB 200GB

Backup 9

10TB10TB

Intact VMs for InstantRestoreTM

Inst

ant R

esto

re

Fast

Bac

kup

Fast

Res

tore



ExaGrid Appliance Storage Architecture



ExaGrid Appliance Storage Architecture



Data Flow for Backup



Data Flow for Deduplication



Data Flow for Restore Recent Data



HSM – Remove Cached Data on Landing Zone



HSM – Remove Cached Data on Landing Zone



Data Flow for Restore Old Data



Deduplication Gotchas Keep compression disabled

Keep encryption disabled

Backup data to same share • Don’t round robin between shares

Keep multiplexing disabled

Backup data to the correct share type

Don’t use it as a fileserver NAS Share• Use backup application to write to ExaGrid

Do not use the backup applications deduplication in conjunction with ExaGrid• If using application’s dedup, it is multiplicative with the ExaGrid’s

Note: As additional full backups land on ExaGrid, overall deduplication ratio rises.



Backup Performance

Concurrent backups into ExaGridClient/Agent performanceData types and affect on performanceNetwork performanceBackup server performance

All of these must be providing optimal performance for a ExaGrid B2D environment to operate at maximum speed.

Most backup environments are optimized for tape and performance issues do not show up until B2D is installed, resulting in the perception of poor performance.



File Types

Data types• Database, email, large or small files, etc.

• Many small files typically limit performance• Directories also affect performance (Document systems)• Few, large files provide very good performance• SQL databases

- Agent vs. SQL dump performance• Exchange agent



MiscellaneousMicrosoft Redirector time out registry key

• Must be applied to all Windows servers that read or write to the ExaGrid

• This increases the default timeout value while the Windows servers are accessing remote shares

Security handled by whitelists

ExaGrid Nics (version 4.6 and below)• Nic1: used for ExaGrid to ExaGrid server communication• Nic2: Used for default gateway (NDP, DNS, alerting) and backups• Nic3 and above – Backups

ExaGrid Nics (version 4.7 and above)• Any Nic can be used for server to server communication,

backups, or both



ReplicationRule of thumb: 3mbit/sec per TB of data being backed up(This is assuming a 2% change rate.)

This must be dedicated to the ExaGrid 24 hours a day. Adjust bandwidth accordingly.

• i.e. If need to black out 12 hours per day than one would need 6mbit/sec per TB of data being backed up.

What might require additional bandwidth:• Compressed data• Higher change rates

A lot of new data or day 1 load (Initial seed will require much higher bandwidth. May need to colocate ExaGrids for initial replication.)



Networking (4.6 and below)Each ExaGrid Site must be on its own VLAN.

One port on the ExaGrid is used in ExaGrid server to ExaGrid server communication (backpanel)

Multicasting is used only between ExaGrid Servers in an ExaGrid Site. Via NIC1, multicast packets must not be routed between ExaGrid Sites.

When setting up a subnet for an ExaGrid Site’s NIC1 port, ensure that standard multicasting protocols such as IGMP/IGMP snooping or multicast routing protocols like DVMRP, PIM, and MOSPF are disabled on the subnet used by your ExaGrid system.

More details: CustomerHWInstall.pdf (Pg. 9)



Networking (4.7 and above)Any port on the ExaGrid can be used in ExaGrid server to ExaGrid server communication

Any port on the ExaGrid can be used for backups

Nic Teaming / bonding is supported

More details: CustomerHWInstall.pdf (Pg. 9)



Networking (4.6 or below)



Networking (4.7 or above)



Troubleshooting Backup Network Environment and Bottlenecks



Client Performance

What to check, troubleshooting• CPU utilization, memory utilization, swap• perfmon, network utilization• Disk utilization, defrag, thrashing

• Can client get data off disk/LUN efficiently?• Network access/contention from client

• Dropped packets, retransmissions, throughput• L2 switching vs. L3 routing for data path

• Run more jobs concurrently with many slow clients• Look at long running jobs and break up

Perform all troubleshooting while client/agent, backup is running



Network Debugging ToolsThe ExaGrid initialization wizard provides tools to help verify your network settings. Click on the icon and the Network Diagnostic page is displayed.

From this page you can use:1. Ping2. Traceroute3. Network interface statistics4. Network performance test

Details on how to use these tools can found on the Network Diagnostics context help page.

These diagnostic tools are also available from the ExaGrid user interface’s Manage drop down menu.

More details: CustomerHWInstall.pdf



Network Performance

Network issues and concerns• Private or public network, speed, contention, etc.• Number of ports for inbound, outbound traffic• Port teaming – inbound to server vs. outbound to ExaGrid• Read vs. write performance and limits• WAN – sufficient bandwidth for replication – use calculator

What to check, troubleshooting• Network switches

• Check statistics on switch ports for maximum peaks- If tested with writefile, should be 90+ MB/s per port

• Verify all settings for unicast storm control, etc. are set at max or disabled (cisco)• Verify flow control is enabled

- Congestion in networks with multiple ports, bottlenecks, and possibility for contention

• Auto-negotiation at correct speed (100Mb/s =12MB/s max)



Network Performance

What to check, troubleshooting• Network

• Utilization, retransmissions, dropped packets - Retransmissions mean network contention, no flow control

• Too much traffic/contention on LAN- Create VLAN or separate network for backup

• Network adaptor on server• TCP offload is enabled• Verify not going through router (L3 vs. L2)

- Use traceroute, etc.



10gigE

Make sure Jumbo Frames are enabled on all required ports• BU servers

• Configurable on switch• ExaGrid servers

• Configurable on switch• Contact ExaGrid support to make mtu change with ExaGrid product

• Etc.



Backup Server PerformanceBU server performance

• How much data can it process• How many concurrent streams• What are limiting factors• What throughput are they getting to tape today (baseline)

• How many concurrent jobs to tape drives (# drives, multiplexing)

What to check, troubleshooting• CPU utilization

• Windows systems: task manager, perfmon• Linux systems: Netstat, ps

• Memory and swap utilization• Insufficient memory and swap will greatly reduce performance

• Network adaptor(s) performance and configuration• TCP offloading, teaming• Driver version



Troubleshooting Practices

Upstream, downstream• Start at backup server

• Verify upstream to ExaGrid for performance- Writefile test to verify bandwidth capacity

• If shared/corp. network run test while backup running- Also watch BU Server network/CPU during test

• Work downstream from BU server through network, agents

Preliminary Performance Testing• Configure to write to disk on the BU Server/NAS

• This will give a preliminary indication of possible performance• If write to disk on the server is slow, there are bottlenecks• If write to disk is fast, speed to us should be fast



Troubleshooting PracticesBackup server limits

• Most Backup Apps• More than 1 BU/Media server may be required• Multiple concurrent jobs are required for maximum throughput

Private network• Separate network for backup traffic

• Additional NIC/Switch, offload traffic from corporate LAN• Improved tape copy with no corporate LAN overhead

• Job scheduling• Concurrent jobs

- Maximize number of concurrent jobs for additional thru-put

Backup server limits • Memory, CPU, and network

• Memory swap during backup• CPU utilization too high• Network card optimization

- Enable flow control, TCP offloading, etc. for performance- Monitor network util, retransmissions, etc.



DBA Section

ExaGrid is backup retention aware-less.

Retention is managed by maintenance plans for direct dumps to ExaGrid.

The DBA is responsible (through a program or manually) to keep deleting files out of retention from the ExaGrid shares just as a regular backup app would.



Thank you for your business

Your dedicated technician is available for you:

[email protected] 800.868.6985 or 508.898.2872, press 2

You may also contact one of our directors of customer support directly:

Paul Doucette, Director of Customer [email protected]

Sam Moukalled, Director of Customer [email protected]

mailto:[email protected]



Date post:	18-Jan-2018
Category:	Documents
Upload:	megan-gibson
View:	222 times
Download:	0 times

TechTarget Backup School New Customer Training | 1 2014 ExaGrid Systems, Inc. Confidential Backup...

Documents