Netbackup 介绍.ppt

备份构架 Server-备份服务器，介质服务器 只是制定备份策略和打包，传输数据到存储池的设备，并不是备份方案的重点 Client-备份数据所在地 Enterprise Client Lan Client SAN Client Agent-备份数据的类型 Option-增强型备份功能 备份构架 * This slide looks at the technologies as they map to RPO and RTO objectives. There’s various strategies/tactics to meet the recovery point objective. Tape backup/restore is on one end of the spectrum with full synchronous data replication at the other end. If a customer can afford a day or more worth of data loss (and they are vaulting everyday) then all they need is tape backup and vault. For customers with more stringent RPO/RTO objectives is where replication should be used. From an RTO objective is a customer can afford to take 1-3 days to come back online they all they need is a tape restore process. They can reduce this time by performing replication only (meaning the data is on disk at the secondary site but they manually bring up the application if a disaster happens). This may take several hours. Finally for the applications with the most stringent RPO/RTO objectives Global Clustering can be used. With this technology the failover process is automatic to get a site up and running in 30 minutes rather then multiple days as seen with a tape restore approach. For example, if it takes 45 minutes to bring applications on line, and the maximum acceptable outage duration is 1 hour, then the Mandatory Decision Point is within 15 minutes of the actual disaster. Need to actually know the maximum acceptable outage duration Clock starts once the disruption occurs How long are end users impacted Business Requirement: Need applications on line in 1 hour. Problem: clock starts upon disaster declaration 1 hour is maximum acceptable outage Time of fault detection eats into IT recovery time Even in a local failure, there’s some time needed to actually detect the fault. Drives the “Mandatory Decision Point” w/i 15 minutes Stress: Still need tape backups Includes support for a NetBackup server, library hosted tape d