Technical Best Practices for Veritas and Microsoft Azure Using a Detailed Reference Architecture
•
1 like•2,228 views
Explore best practices around the following use cases related to the Microsoft Azure platform: Long-term retention of data in the cloud, migration of critical workloads including those running in VMware and Hyper-V, and resiliency of business services running in the cloud. Each of these scenarios are part of what Veritas 360 data management in the cloud can provide. Learn the best way to design, deploy, and manage within each of these scenarios on Azure, and gain key insights into how to avoid pitfalls of common practices and how to boost your cloud ROI – demonstrated via a reference architecture.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Technical Best Practices for Veritas and Microsoft Azure Using a Detailed Reference Architecture
Similar to Technical Best Practices for Veritas and Microsoft Azure Using a Detailed Reference Architecture (20)
More from Veritas Technologies LLC
More from Veritas Technologies LLC (20)
Recently uploaded
Recently uploaded (20)
Technical Best Practices for Veritas and Microsoft Azure Using a Detailed Reference Architecture
- 2. 1 Common Practices and Challenges 2 Best Practices for Data Movement and Long-Term Retention 3 Best Practices for Workload Resiliency and Migration 4 Wrap-Up / Q&A
- 4. Common use cases Disaster RecoveryLong-term Retention Protection in CloudData andWorkload Portability
- 5. Exponential Data Growth Service Level Objectives Operational Inefficiencies Performance & Capacity Environment Coverage Challenges with common approaches
- 7. Organizations can move data to the cloud • Using various protocols such as Object, Block, NFS and CIFS/SMB • Capabilities such as Storage Tiering enables performance and cost optimization by moving data to Hot and Cool tiers • Policy based bi-directional data movement helps to bring back hot data to on-premises storage • Encrypted and secure stream of data sent to cloud Deployment of Access in AZURE to help with Cloud native Apps DR support for NAS workloads with replication across DCs Ensure optimal and flexible data movement to AZURE 1 2 3 Challenges with common approaches to resiliency, migration and long-term retention
- 8. • Low cost • Eliminate tape scale-out • Retain De-duplication NetBackup Media Server NetBackup Media Server Global Dedupe Dedupe Engine Dedupe Engine Dedupe Object Veritas Access SAN DAS Public Cloud over protocol Dedupe Object over protocol
- 9. • Seamless movement of data from on-premises to cool tier • Per storage account limit is 500 TB storage • Access supports 200 storage accounts per user • Automatically allocates additional 500 TB storage account based on space requirements Customer data center Users Master server Media server Media server NetBackup console VPN secured Hot tier Cool tier Deduplicated data Veritas Access scale out storage DeupEngine “on-premises” storage tier “Hot” storage tier “Cool” storage tier Access Lifecycle Policies Protected infrastructure DeupEngine
- 12. Scale-outFileSystem On-premises storage Primary Tier ACCESS Move files that are older than 120 days to AZURE Blob Policy Manager Move files that are older than 90 days to AZURE Blob Access Storage tiering Policy driven
- 13. SAN DAS iSCSIPublic Cloud
- 14. DR support for NAS workloads with replication across DCs Access can be deployed AVMs • To automatically provision the right tier of Azure Storage Disk or Azure Blob tiers. • Works with cloud native applications for both file, object and block based access • Effective resource utilization with thin provisioned storage Deployment of Access in AZURE to help with Cloud native Apps 2 3 Challenges with common approaches to resiliency, migration and long-term retention Ensure optimal and flexible data movement to AZURE 1
- 15. Access Storage Tiering Unstructured data workloads Policy driven SMART IO Thin Provision ProtocolAccess NFS/SMB/FTP) Veritas Access
- 16. Sync/async replication helps to enable DR for application data. Access DR can be enabled in multiple ways: • DR across the regions • DR between On-premises and AVM instances DR support for NAS workloads with replication across DCs 3 Ensure optimal and flexible data movement to AZURE 1 Deployment of Access in AZURE to help with Cloud native Apps 2 Challenges with common approaches to resiliency, migration and long-term retention
- 17. DR with multi-region support Region 2 DR within cloud Access Region 3 Access Storage tiering Unstructured data workloads Policy driven Region 1 Access
- 18. Synch replication Asynch replication Access Storage tiering Unstructured data workloads Policy driven
- 20. Exponential Data Growth Service Level Objectives Operational Inefficiencies Performance & Capacity Environment Coverage Challenges with common approaches
- 21. On-PremisesTraditional or Private Cloud Public or Managed Private Cloud Existing IT Environment • Pre-migration testing • Just-in-time provisioning Single-Click Migration Optimized, secure, data movement ü Pre-migration testing ü Migration automation ü Migration safeguard
- 22. Your Primary Data Center Private Cloud/s Public Cloud/s DR Data Center Single-click disaster recovery, migration and workload mobility
- 23. Predictable, effective and flexible workload resiliency, one time migration and ongoing mobility to/for Azure ü Service Level Objective Driven Configuration ü True Single-Click Recovery for ALL apps ü Optimized Data Movement ü Workload Mobility without data conversion ü Automated Configuration & Provisioning in Azure ü Single console for the Multi-Cloud Operational InefficienciesService Level Objectives
- 24. VM VM VM VM VM VM VM VM VM Resiliency Platform VM VM VM VM Multi-tier dependency mapping & control VM VM VIRTUAL MACHINES MULTI-TIER BUSINESS SERVICES REPLICATION VIRTUAL APPLIANCE INFRASTRUCTURE MANAGER VIRTUAL APPLIANCE Cloud Optimized Secure Data Movement Automated Orchestrated Migration & Takeover Workload Support Data Mover Azure Recovery Compute Azure Recovery Storage VMware VM, Hyper-V VM, Multi-tier VRP Any to Any Data Mover Azure VMs (choice based on workload needs) Managed Disk (blob) Azure VMsManaged Disk/Blob Blob Snapshots Resiliency Platform REPLICATION VIRTUAL APPLIANCE RESILIENCY MANAGER VIRTUAL APPLIANCES Just In Time Recovery Disaster Recovery Rehearsal Azure VMs VM VM VM VM VM VM Environment Coverage Workload Resiliency and Migration to Azure
- 25. 01010110101101010101 00111101011101010110 In-Guest I/O Tap VRP Replication Appliance VRP Replication Appliance Secure (AES 128/256) Bandwidth optimized Optimized bulk transfer • Cross Hypervisor Replication • VMware & HyperV to Public Cloud • Hypervisor Based Replication • Write-Order-Fidelity maintains consistency Production Site Public Cloud IO-Filter - Automatically deployed In-Guest - Taps raw IO-Stream coming from the virtual machines - Relays the data blocks to local replication gateway Replication Gateway (Appliance) - Primary - Virtual appliance hosted in the primary data center - Receives data from IO-Filter - Bulk transfer - batch, compress, encrypt - Pass the data blocks to the corresponding gateway in the pair Replication Gateway (Appliance) - Secondary - Virtual appliance hosted in the secondary data center - Receives data from primary Gateway - Apply data to the cloud volumes Components Performance and Capacity
- 28. ChallengesUse Cases Solutions Common Use Cases, challenges and solutions • Scale considering increasing data growth • Performance & capacity requirements • Service level objectives • Operational efficiency • Long term retention • Data & Workload Portability • Disaster Recovery • Protection in Cloud • Veritas Access: Effective long term retention and data movement to Azure • Veritas Resiliency Platform/ Cloud Mobility: Predictable resiliency, migration and ongoing portability of workloads and business services to Azure
- 29. Education Services • Advisory Services • Design & Deploy • Optimal Efficiency • Product Training • Certification Managed Services • Manage, optimize and protect solutions Consulting Services