1. Copyright © 2018 Arcserve. All rights reserved.
Onboarding Session 3 – Sizing for UDP 6.5 Unified | Simple | Enterprise Class
Dennis Rotsch
Presales Consultant D-A-CH
Stand 13th September 2018
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

2. Copyright © 2018 Arcserve. All rights reserved.
Agenda
90 min
UDP 6.5 Architecture
Overview UDP solution
Building the RPS Server
Building the RPS (Recovery Point Server)
Datastore Locations
Components
UDP Resource Estimator
Example configuration
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

3. UDP 6.5 Architecture

4. Arcserve UDP 6.5 Overview 365 Source
Fast, simple, efficient next-generation data protection & availability
Arcserve UDP is a Snapshot based Backup Solution
It´s support host-based agentless for VMware vSphere & Microsoft Hyper-V and agent-based Windows and Linux operating systems
Globle source side deduplication, encryption, compression & WAN optimized replication
Instant VM & BMR, Lokal & Remote Virtual Standby, Hardware Snapshots, full system High Availability & Tape backup
Supports Windows, Linux, Exchange, SQL, File Server, IIS, AD, Oracle, Pervasive SQL, VMware vSphere, Hyper-V, MSCS
Application consistants Backups & granular Restores
Central Reporting
VIRTUALIZATION HOST VMWare / MS Hyper-V
Physical Server (Database)
Physical Server ( )
Physical Server (File)
Workstation
Share one a NAS
Source
TAPE BACKUP
Backup Repository
Local or network path
CLOUD
RECOVERY POINT SERVER
VIRTUALIZATION HOST VMWare / MS Hyper-V
Destination
Infinite Incremental
Compression
Encryption
Deduplication
CENTRALIZED MANAGEMENT
RECOVERY POINT SERVER
365
Office 365
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

5. UDP 6.5 Architecture – Console & RPS
Management Console
Tape Archive Engine
Source Discovery
Agent Deployment
Reporting
RPS Management
VMware
SDK
SCSI Protocols
Physical Backup
Virtual Backup
Monitoring
RPS
Configuration
Hyper-V
APIs
Cloud SDK
Replication
Virtual Standby
Alerting
Cloud SDK
Instant VM
Other Components
(Future)
UDP
CLI
Central Database
UDP Agent
(Proxy Mode)
Standby
Settings
Status
Plan
Status
Plan
VMware/Hyper-V
UDP
Agent
RPS Server
VM1
VM2
Backup
Data
Global
DeDuplication
Replication
Advanced
Retention
VM3
VM4
Software on Appliance & Cloud

6. UDP 6.5 Architecture – Agent
Production Machine
UDP Web Service
Backup
Browse
File Restore
File Copy
VSS
App Restore
Web Service
Configure Backup and Restores
Catalog
Merge
BMR
Scheduler
Convert VM
Hyper-V
VMware
Remote UI
Read / Write
Disk Access
UDP
Client
Cloud Access
Change Tracking Driver
Arcserve and all other major Cloud providers
Infinite Block Level Incremental Backups Forever
Stand alone Mode or Centrally managed
Client DeDupe
Source
Local Backup
UDP Server

7. Block-level Incremental Backup
Arcserve® UDP
Full
Backup
Infinite Incrementals
Free space
Deduplication
Full Backup A
Incremental A1
Incremental A2
Incremental A3
Incremental A4
Full Backup B
Incremental B1
Incremental B2
Traditional Solution
Infinite Incremental 2
Infinite Incremental 1
Infinite Incremental 4
I2 Technology
Infinite Incremental 3 +
Block level infinite incremental (I2 Technology)TM
Eliminates the need for second full backup
Uses less disk space and network bandwidth
Works in conjunction with global deduplication, compression & encryption to improve backup storage savings & security
Ideal for cloud or remote site protection
Significant backup job merge performance improvements, as only the deduplication index file needs to be updated, when duplicate recovery point data exists

8. How does infinite Incremental work i2 work

9. How does infinite Incremental work i2 work

10. Arcserve UDP Installation
Arcserve UDP Technical Training 101 UDP v6.0 Bootcamp
Arcserve UDP Installation
What can I install together on the same server?  + +    + + +   + + + +  + + + + + 
IMPORTANT!
Ensure server has the required CPU, RAM and Disk resources required for each role.
= UDP Proxy Server
= Arcserve Backup Server
Courseware v1.5 September 2016

11. Building the RPS

12. Copyright © 2018 Arcserve. All rights reserved.
Recovery Point Server
Recovery Point Servers provide:
Global, source-side deduplication
Replication of recovery points to other Recovery Point Servers
Ability to perform Copy-To-Tape for long-term retention
Recovery Point Server must be installed on a server running Windows Server 2008 R2 or later
Recovery Point Server uses data stores for storing backups
Data stores can be on local disk, SAN disk or network disk
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

13. Recovery Point Server: Server Specifications
What are the RPS system requirements?
It depends!
How much data being backed up?
What is the deduplication block size?
What is the deduplication ratio?
What is the data retention?
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

14. Preface Getting it right Where and how we depend on good IOPS Backup
Is all about the right components & size
Depends heavily on the “right” IOPS
Where and how we depend on good IOPS
Backup
Depends heavily on high SSD IOPS
Each block that’s included in a job =
a lookup in hash database
Backup speed is proportional to SSD random IOPS at 4k
This is true until you saturate the network or the agent can’t deliver more read IO from disk
All to be done 100% hands-on

15. Preface
Where and how we depend on good IOPS (input & output per second)
Restore type tasks
(Restore, archive to tape, copy RP & VSB)
All operations here will re-hydrate data
High de-duplication ratio = more random disk IO
Depends heavily on Datastore and Index IOPS
DS IOPS pattern during restore is highly random.
The blocks size also plays a big role here.
Index IOPS pattern is highly random
All to be done 100% hands-on

16. Copyright © 2018 Arcserve. All rights reserved.
The RPS Server Folders
The RPS Server with deduplication, writes the backup data to four directories
Data Store Folder:
Location where recovery point folder structure will be created, share made and source path for restores.
Note: For non-deduplication and deduplication data store, the destination path should be an empty folder.
Data Destination:
Contains the actual deduplicated data.
Defines the data destination folder to save the actual unique data blocks. Use the largest disk to store data as that contains the original data blocks of source.
Index Destination:
Contains “mapping” info for matching deduped blocks to recovery points. Size is typically about 10% of data folder and should ideally be on a separate RAID disk. Faster disk will give better restore and copy-to-tape performance.
Hash Destination:
Contains the hashes for each deduplicated block. Saved to disk, but when RPS is running the full Hash contents need to be held in RAM. Can be on SSD to reduce the amount of RAM required.
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

17. Index Location Index location and it’s role:
It dosn’t have much to do with backup
It will however have a major part in how well
restore and archive to tape performes
To reach a better performance, try to place it on a separate volume

18. Hash location What about using normal disk for the Hash_DB
This is an absolute no can do
The performance will be terrible.
How to calculate Hash Memory
1TB need ~ 10GB physical memory
A customer might say:
I have a very fast array, it should be ok
Ask if it is as fast as a SSD at 4k random read
Most likely it will be 50 to100 times slower
Device
IOPS
Interface
7,2k rpm
~75-100
SATA
10k rpm ~ ~
SAS
15k rpm ~
Intel DC S3500 SSD
75 000

19. Components
CPU
Aim at 2-4 Concurrent active nodes per Core
Note: With the default value (4) there could be up to 16 concurrent active nodes.
If Encryption is used ensure the CPU supports AES-NI
RAM
Suggested Hash memory allocation vs. Datastore capacity
A system that is starved of RAM is a slow system
Note: If some extra RAM is available it could be used as extra cache when SSD is used to store the Hash DB
SSD
Most important property of the SSD is: -> High sustained random 4k IOPS over long time
Drive designed for read intensive operation is ok
Enterprise & Pro-Sumer drives are ok
Intel or Samsung with high MTBF with 24/7 support
Consumer grade drives?: -> Usually not able to deliver stable IOPS over long time

20. Components RAID Controller
Minimum decent controller with onboard battery protected 1GB is what we should aim for.
Always follow the best practise for a given Raid configuration
Raid 5 >> 3, 5 or 9 disks
Raid 6 >> 4, 6 or 10 disks
A larger volume should traverse over to Raid 50 or 60
Number of spindles
Use as many as possible
It’s far better with many small vs a few large drives.
Note: The Arcserve UDP Appliance did show a significant improvement in performance when upgrading from a low end controller “LSI-MegaRAID i” to a more competent model “LSI-MegaRAID SAS i

21. Copyright © 2018 Arcserve. All rights reserved.
NAS Drives
Devices not supporting sparse mode (Cont..)
What does this mean and what is the value?!
When a DS was places on a volumes that didn’t support sparse mode unused blocks wasn’t deleted. Instead we monitored the files in the DS and when a file was 50% empty we copy the used blocks to a new file deleting the old file to free the space.
This as you can imagine had some negative effects on the datastore size.
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

22. NAS Drives Devices not supporting sparse mode.
NAS devices like QNAP etc…
Configurable Reclaim Rebuild Threshold
What does this mean and what is the value?!
When a DS was places on a volumes that didn’t support sparse mode unused blocks wasn’t deleted. Instead we monitored the files in the DS and when a file was 50% empty we copy the used blocks to a new file deleting the old file to free the space.
This as you can imagine had some negative effects on the datastore size.

23. The UDP Resource Estimator Tool

24. The UDP Resource Estimator Tool
Online available
Calculates storage requirements
Provides information about the hardware requirements after 1 year and after 3 years
Weblink UDP Resource Estimator

25. Copyright © 2018 Arcserve. All rights reserved.
Customer Examples
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.

26. Example´s

27. RPS Hardware 3 example sizes & recommendations
Spec / Tier
Small RPS
Medium RPS
Large RPS
Data Protected ***
10 TB
50 TB
100 TB
RAM
16 GB
64 GB
128 GB
CPU
4 cores
8 cores
2 x 8 cores
Usable for Data
3.8 TB
16 TB
 32 TB
SSD
120 GB
240 GB
480 GB
Backup Destination
5 x 1TB - Raid 5
10 x 2TB - Raid 6
4 x 1TB Raid 10
Data Folder
on the same Raid 5
on the same Raid 6
10 x 4TB Raid 6
Index Folder
4 x 2TB - Raid 10
4 x 4TB - Raid 10
Hash Folder
SSD 120
SSD 240
SSD 480
Operating system
2 x 1TB - Raid 1

28. Sample 1 – Single Server environment
Scenario
The Fileserver is backuped with the UDP Agent to the NAS Server
PRIMARY SITE / HQ
Source
Target
FILE SERVER
NAS Storage
Installed UDP Software:
- UDP Agent
Target:
- UNC Path of the NAS Storage
Copyright © 2014 CA. All rights reserved.

29. Sample 2 – Single Hypervisor environment
Scenario
The Hypervisor is backuped with the UDP Agent to the NAS Server
PRIMARY SITE / HQ
Source
Target
Hyper-V
NAS Storage
Installed UDP Software:
- UDP Console
- UDP Agent
Target:
- UNC Path of the NAS Storage
Copyright © 2014 CA. All rights reserved.

30. Sample 3 – Small Environment
Scenario
The hypervisors are backuped agentless
Physical servers are backed up through the UDP agent
Backup workflow: Disk2Disk2Tape
PRIMARY SITE / HQ
Hypervisor - 2 CPU´s
- 10 x Server with MSSQL
Hypervisor - 2 CPU´s
- 30 x File Server
Physical Server - 1 CPU
- Exchange Server
Physical Server - 1 CPU
- Exchange Server
- Assured Recovery
Target
Single Tape
Backup
Installed UDP Software:
- UDP Console
- UDP RPS Server
- UDP Agent
- Arcserve Backup
Target:
- Single Tape Drive
Backup Server 1
UDP CONSOLE
Internal RAID/JBOD
Copyright © 2014 CA. All rights reserved.

31. Sample 4 – Medium Environment
Scenario
The hypervisors are backuped agentless
Physical servers are backed up through the UDP agent
Backup workflow: Disk2Disk2Tape and additionally replicated into a disaster recovery site (RPS to RPS recplication)
PRIMARY SITE / HQ
Hypervisor - 2 CPU´s
- 10 x Server with MSSQL
Hypervisor - 2 CPU´s
- 30 x File Server
Physical Server - 1 CPU
- Exchange Server
Physical Server - 1 CPU
- Exchange Server
- Assured Recovery
Target
Tape Library
Disaster Recovery Site
Backup Server 1
UDP CONSOLE
Backup Server 2
Installed UDP Software:
- UDP Konsole
- UDP RPS Server
- UDP Agent
- Arcserve Backup
Target:
- UDP RPS Server
- Tape Library
Installed UDP Software:
- UDP RPS Server
- UDP Agent
Target:
- UDP RPS Server
Copyright © 2014 CA. All rights reserved.

32. Sample 5 – Mid. Large Environment
Scenario
The hypervisors are backuped agentless
Physical servers are backed up through the UDP agent
Backup workflow: Disk2Disk and additionally the RPS Servers replicate each other
PRIMARY SITE / HQ
Target
UDP CONSOLE
Installed UDP Software:
- UDP Console
- UDP RPS Server
- UDP Agent
Target:
- UDP RPS Server
Hypervisor - 2 CPU´s
- 50 VMs
RECOVERY POINT SERVER
Hypervisor - 2 CPU´s
- 30 x VMs
Installed UDP Software:
- UDP RPS Server
- UDP Agent
Target:
- UDP RPS Server
Hypervisor - 2 CPU´s
- 30 x VMs
RECOVERY POINT SERVER
Hypervisor - 2 CPU´s
- 30 x VMs

33. Sample 5 – Large Environment
Scenario
The hypervisors are backuped agentless
Physical servers are backed up through the UDP agent
Backup workflow: Disk2Disk2 and additionally replicated into a disaster recovery site
Primary Site / HQ
Target
Disaster Recovery Site
UDP CONSOLE
Installed UDP Software:
- UDP Console
- UDP RPS Server
- UDP Agent
Target:
Hypervisor - 2 CPU´s
- 50 VMs
RECOVERY POINT SERVER
RECOVERY POINT SERVER
Hypervisor - 2 CPU´s
- 30 x VMs
RECOVERY POINT SERVER
Installed UDP Software:
- UDP RPS Server
- UDP Agent
Target:
Hypervisor - 2 CPU´s
- 30 x VMs
RECOVERY POINT SERVER
Hypervisor - 2 CPU´s
- 30 x VMs

34. Copyright © 2018 Arcserve. All rights reserved.
Questions ?
Dennis Rotsch
Presales Consultant D-A-CH
8/30/2019
Copyright © 2018 Arcserve. All rights reserved.