migrating from tara to dsa - amazon s3 · #tdpartners16 georgia world congress center migrating...
TRANSCRIPT
#TDPARTNERS16 GEORGIA WORLD CONGRESS CENTER
Migrating from TARA to DSAImplementation Considerations
Ram Koralla / John MelerAdvisor Teradata DBA, Anthem/ Senior Technical Consultant, Teradata
1. Problem Statement2. Environment Before Upgrade3. Upgrade Plan4. Test Results5. Issues Encountered6. Limitations7. BAR Environment with Old and New Hardware8. Future Plans
Agenda
2
Problem Statement
3
Migrate BAR Environment to Data Stream Architecture “DSA” for Performance
• Current Media Server and network hardware not supported by DSA
• Running out of capacity in tape library• Cannot Incrementally migrate TD Systems or Jobs to new
hardware • Drives & Media Servers are shared between systems
• Backups and Restore Schedule cannot be interrupted• Scheduled outages allowed once week for
implementation
Environment Before Upgrade
4
Current Backup Details
5
Backup size per Week• 800+ Terabytes
Restore size per Week• 10 Terabytes
Vaulting• 20 Vault Profiles• 400 Terabytes• 220 Tapes
NetBackup• 600 new Policies• 51 Tape Drives (SL8500)
Upgrade Plan
6
Phase 1 & 2Upgrade BAR Hardware
Phase 3Migrate TARA Jobs
Phase 4Rewrite Jobs for DSA
Phase 5Migrate DSA jobs to Disk
Phase 1 – Upgrade BAR Hardware
7
Upgrade Master Server Hardware – Outage Required• Replace with DSADSC Server• Migrate Netbackup Catalog• Migrate TaraServer Directories• Update NBU and TARA configuration• No changes to existing TARA jobs.
Phase 2 – Upgrade BAR Hardware
8
Add New Media Servers to Domain• Install NBU and TARA software• Update NBU and TARA configurations• Test with backup to local disk on media servers• Legacy media servers still running production backups
Migrate BAR Private Network to Bynet v5 as TD Systems are Replaced
Phase 3 – Migrate TARA Jobs
9
Re-architect TARA jobs for fewer media servers• Client groups simplify creation and maintenance• Redesign BAR Private Network for Client Groups
• 1 GbE network migrated
Create new TARA Jobs• Create policies with dummy storage units
• Create Linux scripts to generate Policies• Create Client Groups and Jobs with dummy Policies
Phase 3 – Migrate TARA Jobs …
10
Re-architect Vaulting• Create profiles using dummy policies• Adjust profile scheduling to match new job scheduling
Switch Backups to new media servers – Outage Required• Switch Library connections to New Media Server
• Regenerate policies with actual Storage Units• Re-IP TD nodes and connections for new BAR Private
network design• Activate new backup and vaulting schedules
Phase 4 – Rewrite Jobs for DSA
11
Re-architect TARA jobs for DSA• Gradual transition• Map Client Groups to Target Groups
• One Stream per tape device• Redesigned BAR Private Network Optimal for Target
Groups
Phase 5 – Migrate DSA Jobs to Disk
12
Re-architect DSA Jobs for Disk storage• Optimize for deduplication
• One Stream per AMP• Test multiple backup generations per job
Re-architect Vaulting• Modify profiles to vault increased streams• Adjust retentions based on disk space• Adjust Vaulting schedule based on retentions
• Delete from disk after vaulting
DSA Test Results and Comparison
13
Comparison between TARA & DSA
• Runtimes vary between 30%-60% less with DSA
• Tape usage reduced 50% for Dev/Test systems using Block Level Compression.
• Script migration still in progress.
DSA Test Results and Comparison …
14
Comparison Test Data between TARA and DSA
TARA Job:Total Runtime: 28 minutesSize: 1.4 TB
DSA job:Total Runtime: 15 minutesSize: 341 GB
Issues Encountered
15
Encountered the following issues during configuration:
• HSN and Channel Nodes are not connected to CLAN or BAR network
• No Room on Switches and added nodes using CLAN
• TCP/IP ports opened on CLAN
Limitations
16
• All objects in the job are locked at beginning of job
• Scripting and editing of jobs is awkward with XML
• Backup objects not tracked in DBC.RC Event table
• Need to Export the log file of a job to a csv file and load to table.
• Difficult to check job details while job is executing.
BAR Environment with Old and New Hardware
17
• New Media Servers
• Existing Tape Library (SL8500)
• Existing Tape Drives
• Existing Tapes
• Existing OKM
BAR Environment with Old and New Hardware …
18
Future Plans
19
• Upgrade to DSA 15.11
• Move to Data Domain
• Re-architect DSA jobs for Data Domain
• Automate restore of data to Disaster Recovery site.
#TDPARTNERS16 GEORGIA WORLD CONGRESS CENTER20
Thank You
Questions/CommentsEmail:
Follow MeTwitter @
Rate This Session # with the PARTNERS Mobile App
Remember To Share Your Virtual Passes
Ramakrishna Koralla: [email protected] Meler: [email protected]
746
21