Presentation is loading. Please wait.

Presentation is loading. Please wait.

EMC Avamar 6.1 Release April 2012.

Similar presentations


Presentation on theme: "EMC Avamar 6.1 Release April 2012."— Presentation transcript:

1 EMC Avamar 6.1 Release April 2012

2 Agenda Avamar 6.1 Overview Extended Retention Overview New features
Beta results Positioning/Use Cases/Pricing/Licensing Performance metrics Sizing Guidelines Extended Retention Overview Feature Overview (appliance and software) Comparatives between ADT/AST/ATO

3 Avamar 6.1 Release Summary
Avamar Management, Security & Supportability Improved management including LDAP/AD group authentication* more granular backup scheduling*, and node add/replace from the UI* Enhanced supportability including hardware fault detection in Avamar GEN4 switches* and clear/concise descriptions for new error/event codes* Improved encryption including client-server encryption using FIPS validated encryption*, key rotation for encryption of data at rest Performance & Efficiency Avamar multi-stream expansion - for SQL, SAP, Sybase & Hyper-V Data Domain – DD Boost Multi-stream for SQL, Oracle, Exchange, SAP, SharePoint, Sybase & Hyper-V; DD Boost single stream for DB2 Increased client-server connection limit to at least 30 per node (A 16 node server should support 480 (30x16) connections) Avamar Server startup/shutdown performance improvements Improved DT/LT Support Privileged users have more control over their policy Ability to specify that the last version of a file backup never be deleted Qualify with IE 9 and Mac OS X 10.7 Expanded Avamar Client Support Updated OS Support - Windows Disaster Recovery 64-bit ISO, CentOS 6, Debian 6, Oracle Enterprise Linux 6 & Apple OS X 10.7 New Avamar SAP & Sybase Protection Improved DB2, Lotus and Oracle Protection Improved Microsoft Protection – Exchange federated backups, Exchange incremental backups, SQL Server 2011 (Denali) support, multiple SQL backup/recovery TCE improvements Support for Enterprise Vault 9.x/8.x Command Line Interface (CLI) support for Application Plug-ins Virtualization VMware –Disk-level granularity to backup and restore, Universal image proxy, File level Restore from an Image-level Backup for Linux, Thin-provisioned recovery, Universal File Level Recovery (FLR) Proxy and Avamar management console command line interface (CLI) support New Hyper-V Protection – including image-level backups for image and file level recoveries, Avamar multi-stream & DD Boost support for performance Avamar Extended Retention to Tape or VTL Export from Data Store to physical tape, Export from DD to physical tape, Export from Data Store to DD as VTL and Export from DD to DD as VTL

4 Avamar 6.1 Release Management, Supportability, Encryption
Avamar Server Management LDAP/AD group authentication More granular backup scheduling Node add/replace from the UI Enhanced supportability Hardware fault detection in Avamar GEN4 switches Clear/concise descriptions for new error/event codes Improved encryption Client-server encryption using FIPS validated encryption Key rotation for encryption of data at rest

5 Avamar Grid Performance
Increased client-server connection limit from 18 to 27 per node means higher throughput and faster backups Increased total number of concurrent connections per Avamar grid so that a full 16-node grid can use all connections for maximum backup performance Faster Avamar Server startup Faster Avamar Server shutdown Waiting on some performance numbers.

6 Updated Data Domain Integration
Primary Avamar Server Replica Avamar Server Avamar Backup Application NAS Avamar Clients Client Backups, Metadata Replication ROBO Metadata NEW VM All replication topologies are supported Management Phase 1: Exchange, SharePoint, SQL Server, Oracle, VMware images Phase 2: DB2, Sybase, SAP, Hyper-V DB Avamar Clients DDA DD Boost Database, VM Image Backups Replication SharePoint Multi-stream support All client options are supported (e.g., granular level recoveries) Primary Data Domain System Replica Data Domain System NEW

7 Multi-Stream Performance
Faster backup throughput with Avamar multi-stream expansion Added: SQL, SAP, Sybase & Hyper-V Existing: Oracle, Exchange, SharePoint New multi-stream support for faster backups to Data Domain systems through DD Boost SQL, SAP, Sybase & Hyper-V Oracle, Exchange, SharePoint Faster backups through multi-streaming. Added SQL, SAP, Sybase and Hyper-V for Avamar, which joins existing multi-threaded backups for Oracle, Exchange and Sharepoint. Now Data Domain can receive multi=streaming for all selected workloads as listed here. Note that there is still only a single stream for VMware Images and IBM DB2. (Also note that Lotus notes for DD will be added in 2013).

8 New Features for Exchange & SharePoint
Exchange Server 2010 DAG Federated Backups Exchange Incremental Backup RSG/RDB Management Retirement of Exchange Legacy Plug-in SharePoint Retirement of SharePoint Legacy Plug-in

9 Exchange DAG Federated Backups
Preferred Server order list: MBX3, MBX2, MBX1

10 New Features for SQL SQL Plug-in Enhancements
Up to 4X faster backups and recoveries via multi-stream backups to Avamar Grids or Data Domain Systems Support for SQL Server 2012 Including AlwaysOn Availability Group support Enhanced SQL Backup & Recovery Skip or promote SQL simple mode DBs during incrementals GUI based recoveries for SQL FileGroups & files SQL ‘NORECOVERY’ & ‘STANDBY’ recovery options Simplified SQL database naming during recoveries CLI support for backup & recovery operations

11 New Features for Oracle
Independent Log and DB backups Complies with DBA requirements and common use models Multiple log backups DB backup daily, weekly Corrupted block detection for faster recovery Restore specific good blocks to replace corrupted blocks Flashback Database Recovery Fast recoveries to any point-in-time, through the Avamar GUI DD Boost multi-stream support increases throughput for faster DB backup Oracle: Log backups: many customers prefer to backup their database transaction logs more frequently than their actual database. As an example, backup the database once per day or perhaps every other day, but backup the log files every 2 or 4 hours – to free up primary storage space. With Avamar 6.1, we disassociate the backup of databases and logs; backups of db’s and logs can be scheduled and configured separately. Oracle: Corrupted bock detection & recovery: Oracle can detect its corrupted block, and Avamar 6.1 can recover only the corrupted blocks. There is no need to recover or rollback a tablespace or an entire database. Oracle: Flash recovery area integration: Flash Recovery Area (FRA) is a disk location used by Oracle for backup/recovery without the use of a backup software. Oracle manages the FRA itself, e.g. it retains the files only as long as they are needed for recoveries, etc. Avamar 6.1 offers integration with Oracle’s FRA, as it performs “usual” RMAN backup, but from the FRA area rather than from the Oracle database itself. Multi-stream to Avamar Data Store or Data Domain system.

12 New SAP Support Fully Featured High Performance Backup via GUI
Full, partial, incremental &  logs “Hot” (on-line) and “Cold” (off-line) Fully Featured Faster Recovery via CLI Full, granular and logs Relocated restore (i.e. to different location or host) Multi-stream support increases backup performance to Avamar Data Store and Data Domain Systems Active/Passive cluster support for the enterprise Can restore, from any host of the cluster, without knowing which physical host was used for backup Support all versions of SAP (7.00, 7.10, 7.20) Supports all current versions of Oracle supported by all current versions of SAP BR*Tools which enables scripting OS Support in-sync with SAP OS Support Supports all current versions of RedHat, SuSE, Solaris and Windows, 32-bit and 64-bit supported by SAP We offer first-class, feature-rich support for SAP environments. Broad coverage: *all* current versions of SAP 7.00, 7.10, 7.20 *all* current versions of SAP BR*Tools SAP BR*Tools 7.00, 7.10, 7,20 on *all* bitnesses of *all* versions of *all*l tier-1 OS’s 32-bit and 64-bit for: RHEL 4, RHEL 5, RHEL 6, SuSE 10, SuSE 11, Solaris SPARC 9, Solaris SPARC 10, Win 2003, Win 2003 R2, Win 2008, Win 2008 R2 *All* of the features below are offered on *all* SAP environments above: Customers can back the entire, or only part, or only the logs of the SAP environment Customers can shut down their SAP and back it up, or they can do their backups while the SAP is up and running Customers can perform their SAP backups via the standard Avamar GUI, and recoveries only via the CLI Customers can recover their entire SAP database, or do a Granular Lever Recovery of it (i.e. they can recover only a subset of what they’ve backed up) Customers can perform either single-stream or multi-stream backups and restores, to the Avamar Data Store and to a Data Domain system Active/passive (failover) clustered environments, for SAP is supported Non-English UTF8 SAP installations are supported.

13 New Sybase Support Fully Featured High Performance Backup via GUI/CLI
Full, partial, incremental &  logs “Hot” (on-line) and “Cold” (off-line) Fully Featured Faster Recovery via GUI/CLI Full, granular and logs Relocated restore (i.e. to different location or host) Multi-stream support increases backup performance to Avamar Data Store and Data Domain systems Active/Passive cluster support for the enterprise Can restore from any host of the cluster without knowing which physical host was used for backup Support all versions of Sybase ASE (15.0.x, 15.5.x) OS Support in-sync with Sybase OS support Supports all current versions of RedHat, SuSE, Solaris and Windows, 32-bit and 64-bit supported by Sybase We offer first-class, feature-rich support -- for Sybase environments. Broad coverage: *all* current versions of Sybase Sybase ASE 15.0.x, 15.5.x on *all* bitnesses of *all* versions of *all*l tier-1 OS’s 32-bit and 64-bit for: RHEL 4, RHEL 5, RHEL 6, SuSE 10, SuSE 11, Solaris SPARC 9, Solaris SPARC 10, Win 2003, Win 2003 R2, Win 2008, Win 2008 R2 *All* of the features below are offered on *all* SyBase environments above: Customers can back the entire, or only part, or only the logs of the Sybase environment Customers can shut down their Sybase and back it up, or they can do their backups while the Sybase is up and running Customers can perform their Sybase backups and restores via the standard Avamar GUI, or via the CLI – whatever works for them best. Customers can recover their entire Sybase database, or do a Granular Lever Recovery of it (i.e. they can recover only a subset of what they’ve backed up) Customers can perform either single-stream or multi-stream backups and restores, to the Avamar Data Store and to a Data Domain system Active/passive (failover) clustered environments, for Sybase is supported Non-English UTF8 Sybase installations are supported.

14 Lotus & DB2 Plug-ins Lotus DB2 Recovery via CLI Internationalization
DPF support Parallel servers for increased performance Granular Level Recovery (GLR) Faster restores Enable specific table to be restored instead of entire DB Recovery via CLI Relocated recovery To a different location or host Lotus: recovery via CLI: self-explanatory; you can recover from the command-line, in case you need extra power/flexibility. Lotus: I18N support: Lotus plugin now offers UTF8 support for Lotus environments, to the extent supported by the Avamar filesystem client DB2: DPF support: DPF is DB’2 version of a “parallel server”, leading to increased performance. We now support these DB2 “parallel servers”. DB2: granular recovery: GLR is now an option in the Avamar recovery GUI. Customer can restore one or more tablespace, out of an entire database backup. Not only the recovery is faster than before, but the recovery/repair of the database is more targeted (e.g. if a table is deleted accidentally, and DBA realizes that 3hrs later, only the deleted tablespace has to be recovered whereas the rest of the database remains intact and it’s not rolled back to the time of the tablespace deletion). DB2: Recovery via CLI. This statement is incorrect, and it should be changed to “Backup and Recovery via CLI”. Sophisticated customers may prefer the flexibility and power of a Command Line Interface for the ad-hoc backups and restores. Other customers may have their own scheduler, to which they can plugin Avamar only if Avamar supports backups via CLI. As another user case, in the unlikely event that our GUI has a bug, customers want to fall back to a CLI interface. Avamar 6.1 now solves all these problems, by offering CLI support for both backup & restores. DB2: Relocated recover: A backed up database can be recovered to a different location on the same host, or to a different host (e.g. in case of disaster recovery).

15 New Features for VMWare
Faster recovery with file level restore from an image backup for Linux Disk-level granularity to backup and restore Provides flexible backup and recovery options Backup individual .vmdk and config files Minimize backup and recovery windows by only protecting what is necessary Universal image proxy for easier management of mixed environments Protect both Linux and Windows VMs with a single proxy Restore both Windows and Linux files with a single proxy

16 New Features for VMWare
Thin-provisioned recovery Thin provisioned VMs are restored thin, as opposed to thick Universal File Level Recovery (FLR) Proxy Restore both Windows and Linux files with a single proxy Avamar management console command line interface (MCCLI) support Discover clients Add new VM clients (vCenter/Proxy/VMs) Proxy configuration Recovery to the same VM (in-place) Recovery to new VM (out of place)

17 New Hyper-V Support Full virtual server protection
Guest level backup and recovery Application-aware protection for Exchange, SQL, SharePoint, etc. Fine-grained recoveries Hyper-V Image backup and restore Disaster recovery Complete protection of virtual hard disk (VHD) files Recover guests to alternate Hyper-V servers Granular Level Recoveries (GLR) from image backups in minutes IN-GUEST From a Avamar perspective you get all the benefit of deduplication, and a full range of backup and recovery services for Microsoft Hyper-V and Hyper-V R2. NetWorker targets everything you need to ensure complete recovery, including protection of Virtual Hard Disks (VHDs) as well as the operating system components—things like system state, data volumes, and the Hyper-V configuration database. In the parent partition or virtual server host—now called the management operating system—NetWorker leverages the Hyper-V VSS Writer to deliver disaster recovery for Hyper-V servers, capturing Virtual Hard Disk files that make up the Hyper-V guests and support all of the server platforms that Microsoft is shipping that support Hyper-V. NetWorker can also be used in the guest or child partitions to deliver application-aware backup with fine-grained recovery. In this case, in the guests, NetWorker application intelligence is leveraged to target application-consistent protection, which also delivers fine-grained recovery for applications.

18 Windows Server Hyper-V
Hyper-V Image Backup Complete Hyper-V Protection Protects OS, System State, Data Volumes & Hyper-V Configuration Database Full Image Backups of Hyper-V Guests offering DR and granular protection Supports all Hyper-V Guest Operating Systems Windows Server 2008R2/2008, Windows Server 2003, Windows 7, Windows Vista, XP, SUSE Linux Leverages Hyper-V VSS Writer Quiesces Windows OS and Applications within guest for OS & application consistency No requirements for in-guest Avamar software Flexible Hyper-V Backup Options Support for stand-alone Hyper-V Servers Federated Hyper-V Cluster Shared Volume CSV) Backup Backup to Avamar grid or Data Domain Systems Multi-stream backups to Avamar grids or Data Domain via DD Boost Virtual Machines APP OS APP OS APP OS Windows Server Hyper-V Physical Server

19 Federated Hyper-V CSV Backup
Federated Hyper-V CSV Backup Support Scheduled VM backups from the CSV Cluster Supports live migration of VM’s to different Hyper-V CSV node Flexible CSV Backup Scheduling Backup all VM’s in the CSV cluster Backup Individual VM’s

20 Hyper-V Image Recovery
Physical Server Virtual Machines APP OS Windows Server Hyper-V

21 Hyper-V Granular Level Recoveries (GLR)
Avamar Hyper-V Granular Level Recovery (GLR) Proxy Mount Hyper-V Image backups quickly from within Avamar & Data Domain savesets to recover guest level folders and files

22 New Features for Desktop/Laptop
Improved DT/LT Support Privileged users have more control over their policy Persistently override backup dataset and schedule Option to specify that the last version of a file backup never be deleted Prevents backups from expiring during extended time off/leave of absence Change tray icon color based on status of last backup Support for cross Mac <-> Windows restores Option to not backup on wireless Qualify DT/LT on IE 9, Mac OS X 10.7 Add client type in Home stats to better track DT/LT installs Small changes Preference to set default start page to search or browse New property to disable restore from alternate computer Limit the number of on-demand backups per day Prevent user from queuing multiple restores Privileged users have more control over their policy When enabled by the Avamar admin, users can change the dataset that gets backed up by scheduled backups. They can also change the scheduled start time, but remember, this really only controls when a backup job is ‘submitted’. If there are other jobs in the queue, this backup may not start immediately. Option to specify that the last version of a file backup never be deleted To prevent a users backups from expiring, a backup must be run at least once before retention expires. This feature allows the admin to set a global flag to prevent the last version of each file from falling of the end, and supports long vacations or leaves of absence Change tray icon color based on status of last backup The icon will now provide a color coded indication of status, with green, yellow or red checkmarks super-imposed on the Avamar icon to represent success, warning or error. Support for cross Mac <-> Windows restores Option to not backup on wireless This feature was implemented to support users who get charged for wireless usage. Since we are unable to differentiate between different wireless types (mobile phone vs WIFI) the user must be careful to set this properly to avoid significant phone bills. Qualify DT/LT on IE 9, Mac OS X 10.7 Add client type in Home stats to better track DT/LT installs Small changes Preference to set default start page to search or browse This feature is to support customers used to navigation trees who would prefer to start with our browse interface New property to disable restore from alternate computer This feature is to support security conscious customers who do not want to allow restore from an alternate computer Limit the number of on-demand backups per day This feature is to prevent overloading the server because of too many on-demand backups Prevent user from queuing multiple restores This feature is to prevent impatient users from queuing the same request over and over if a restore does not start immediately

23 Extended Retention

24 What is Avamar Extended Retention?
An Avamar 6.1 feature allowing selected Avamar backups to be automatically exported to tape / virtual tape for long-term retention periods 30-90 day retention Multi-year retention Management UI Avamar Server Tape Library or VTL Media Access Node All SW hosted on Media Access node Administrative/monitoring UI Streaming engine Library management Restore server Solution is a read-only operation against Avamar – does not expire data on the grid (that is under exclusive control of Avamar) Export asks Avamar to generate a restore stream, streams it to target device without staging agnostic to what backend Avamar device it is coming from contains all data (not deduplicated) written to target device in fully “re-hydrated” format (blind to what target device does with it (dedupe, encryption, etc) Restores are 2-step Import reads data off tape into internal Avamar instance (Restore Server) within Media Access node Restoring to target machine performed through standard Avamar Administrator associated with Restore Server Does not involve original Avamar Server at all SW license included in Avamar licenses Data Store Data Domain

25 Scalability One Media Access Node supports up to five grids
One Media Access Node supports up to eight devices Media Access Node

26 Extended Retention Intuitive user menus and wizards
Avamar Administrator Automated device discovery and configuration 100% recovery of permissions, Access Control Lists and other attributes to ensure security is enforced as originally set Supports offsite restores for eDiscovery REQUIRES AVAMAR 6.1 ACL stands for “Access Control List”, a more powerful way to define who can read/write and do other things to a file or directory than the standard OS permissions. These ACLs are stored by the OS as extended attributes of a file, as are other attributes an OS may allow a user to use or define (such as Window’s ability to define certain properties of each file such as Author, etc. – right-click on a file and open “Properties” and see the list of attributes Windows supports). Backup products must handle these attributes and restore them accurately to honor security measures and other things using these attributes. SCSI-based libraries/robots & VTLs is a generic description of the salient characteristics of physical tape libraries we will support. A precise list will be in the Avamar 6.1 Compatibility Matrix doc, but this section alone is a dozen pages long. The Media Access node is a new node type in the Data Store Gen4 family – different from all others. There are a couple specs that could be relevant here – and that is the connector type and speed of the FC interface.

27 Questions and Answers

28 Thank you.


Download ppt "EMC Avamar 6.1 Release April 2012."

Similar presentations


Ads by Google