Rosario evento a clientes de RMDM Octubre 2009 - RM
1. Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles. DATE text box is not on master and can be deleted. The date should always be 20 pts. RECOVERY MANAGEMENTOctubre 2009 Santiago Cavanna. Information Security Consultant.
19. ARCserve Backup r12.5 Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles No DATE on divider pages.
21. CA ARCserve Backup r12.5 Nuevas funcionalidades clave Protección completa para VM Recuperación granular desde backup de imagen Soporte para VMware, Microsoft Virtual Server 2008 / HYPER-V Eliminación de datos duplicados Reduce el espacio para backup Consola Vista gráfica de su entorno de backup Soporte para Oracle RMAN y plataformas de 64 bits Soporte para modo basado en archivos y RMAN Soporte para x64 e IA64 bits Control y auditoría de accesos Diferentes roles con permisos específicos Registro de auditoría de operaciones críticas Administración de contraseñas Administración de contraseñas para backups encriptados y clientes de backup Garantía de medios Garantiza que los datos de backup en los medios puedan ser leídos y editados Paquetes de implementación de agentes Implementan agentes en múltiples hosts remotos simultáneamente 11
41. CA XOsoft conduce la protección de datos y la disponibilidad de las informaciones.
42.
43.
44. Eliminación de datos duplicados en ARCserve Eliminación de datos duplicados en el servidor de backup Eliminación de datos duplicados en el servidor de producción Eliminación de datos duplicados a nivel de bloque Eliminación de datos duplicados a nivel de archivo Eliminación de datos duplicados a nivel de bloque y optimizado, cuando sea posible, a nivel de archivo Eliminación de datos duplicados en línea Eliminación de datos duplicados luego del proceso Eliminación de datos duplicados en línea y luego del proceso 18 Eliminación de datosduplicados
45. Eliminación de datos duplicados global ARCserve reconoce que puede haber redundancias notables en el C:de diferentes máquinas. A su vez, luego de que se realiza el backup de la eliminación de duplicados en línea, ARCserve inicia un proceso de eliminación de duplicados global luego del backup. Esto eliminará duplicados en las unidades C:de diferentes máquinas (como P1, P2, P3) y encontrar redundancias. 19 P2 C:br />X:br />SQL DB1 SQL DB2 P3 C:br />X:br />EXCH SG1 EXCH SG2 P1 C:br />D:br />X:br />Y:br />SERVIDOR DE BACKUP Eliminación de datosduplicados
46. Consola¡NUEVO! Vista gráfica de su entorno de backup 20 Comprensión, resolución de problemas, planificación y reportes sencillos para el entorno de backup Ayuda a planificar las compras y el presupuesto Información sobre hardware del sistema Uso de volumen, disco, CPU, RAM… Físico o virtual Información sobre software Nivel de SO/parche Versiones de agentes de ARCserve Reportes y análisis gráficos más allá del backup de la aplicación Recolección, análisis, correlación y reportes (SO, red, disco, hardware, etc.) Reportes orientados al negocio (RPO/RTO, uso del hardware, etc.)
54. Paquetes de implementación de agentes Más fácil de implementar 26 Instala y actualiza agentes sobre múltiples hosts remotos simultáneamente Garantiza la presencia de los agentes de las versiones más actuales en su entorno de backup
55. CA ARCserve Backup r12.5 Competitive Comparison CA ARCserve Backup r12.5 Competitive Comparison Leading technologyOffers technology XDoes not offer today †Additional Options Required 27
57. Email Server Suite 29 CA ARCserve Sales Overview March 2009 Email, Database & Application Suites Application Server Suite Database Server Suite File Server Suite File Server Suite File Server Suite Exchange (Exchange Premium Add-On) Lotus Notes MS SQL Oracle Sybase Informix SAP MS SharePoint 29
66. Novedades de r12.5 Nueva protección de aplicaciones y sistemas Configuración de alta disponibilidad/RD para Microsoft SharePoint 2007 Configuración de alta disponibilidad para el Servicio de Control de CA XOsoft Protección del estado de sistema Windows Sincronización de registros Windows Mejoras en la virtualización Configuración de alta disponibilidad para VMware vCenter Replicación a nivel de host para Microsoft Hyper-V Soporte entre plataformas CA XOsoft Replication para UNIX/Linux Mejoras adicionales Ajuste del ancho de banda Motor nativo de 64 bits Localización e internationalización Inglés, francés, alemán, italiano, español, portugués brasileño, chino (simplificado), chino (tradicional) y japonés
67.
68. Replicación y altadisponibilidadparaSharePoint 2007 Brinda replicación y alta disponibilidad integradas y basadas en aplicaciones para la implementación independiente (todo en uno) de SharePoint 2007 Brinda soporte para SharePoint Server 2007 Interacciones simplificadas para usuarios Identificación automática de datos para SharePoint Configuración automática de réplicas para SharePoint Favoritos consistentes para SharePoint (VSS) Prueba de CA XOsoft Assured Recovery
74. Brinda soporte para la creación de favoritos periódicos que actúan como puntos de rebobinado consistentes con la aplicación
75. En un escenario de HA, puede detectar la falta de disponibilidad de una VM de origen e inicia la VM sobre el servidor de réplica sin intervención del usuario
76. HA no sólo confirma que la VM está funcionando sino que también verifica que esté accesible desde la red
77.
78. Integración CA XOSoft r12.5 + CA ARCserve r12.5
79. Integración XOSoft r12.5 y CA ARCserve r12.5 CA ARCserve provee el beneficio de un Backup tradicional CA XOsoft provee el beneficio de la protección continua de datos + La Integración provee el doble beneficio: La protección continua de datos and y el Backup de estos Datos protegidos.
82. Roadmap Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles. No DATE on divider pages.
96. Licenciamiento optimizadoRoadmap Information - For Information Purposes Only. Subject to Change without Notice and does not affect the rights or obligations of CA or its licensees. Please see legal notice attached to this presentation for more information.
97. Muchas Gracias !!! Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles. No DATE on divider pages.
Hinweis der Redaktion
This slide clearly demonstrates why you need to think about Recovery Point Objectives (RPO) and Recovery Time Objectives (RTO) with your data and key applications.This slides represents a 24 Hour Windows of Time,Typically most customers today backup their data every evening when the users go home, or backup systems hot every 24 hours. Most customers believe that this is a sufficient way of protecting their critical data as this is the way we have always done it and is regarded as a standard or “best practice” for system backups.In reality this may not be sufficient for many of your key systems, by only backing up the data once every 24 Hours means that data that is added or changed between backup Windows is at high risk.If you take a scenario that one of your systems fail at 2 PM in the afternoon, (this could be your email or SQL database or IIS Web transaction server).The IT Manager has two big concerns he needs to think about!RPO – Because I only backup my data every 24 Hours in the evening, The best case scenario I face is that all the data that has changed since 8 PM the evening before (when the backup was taken) will be lost.RTO – If I am recovering from Disk or Tape it could take maybe 4 Hours + to recover my 2 TB email or Database system using my backup software.So in summary, an outage in the middle of the day has cost me 24 hours of service, This is because the data I recovered was taken from the backup the day before and it took me 4 hours + to recover my data which meant my users could not use the system for the remainder of the day.Is this scenario acceptable for your email, Critical Database, ERP or Web Systems?By using an intelligent combination of Data Replication, CDP, and High Availability, I could have protected my self from the following two scenarios:If the server was functioning and we had experienced an application data corruption: IT could carry out a CDP “Data Rewind” and selected an automatic checkpoint taken just prior to the outage, then rewound the application to that point in time and restarted the system.B) If the server hardware had failed: Failed over the System immediately to a standby server which has a mirrored copy of my production data and returned service to the users within minutes.
Introduced by VMware 3.0 to avoid performance impact on ESX server/VMs while simultaneous network backups are going on
Limited user profiles – this will help the customers create multiple users with different privileges for ARCserve functionality; the customers will be able to use Windows accounts as ARCserve users and Windows passwords with it. A limited auditing will also be provided – this will tell the end user about the operations performed by ARCserve users (including login details)Password management for encrypted backups – helps the user in recovering data that is encrypted – don’t need to remember the passwords that could be changing every month.The customers will be able to submit backups with the option of ARCserve remembering the password for recovery purposes – this will ease the recovery processPassword management for backup clients – ARCserve will store the user/password for all backup clients; this will help the user to submit backups and restores (especially with user profiles) without the restore operator knowing the user/password of the server (to be restored)
Limited user profiles – this will help the customers create multiple users with different privileges for ARCserve functionality; the customers will be able to use Windows accounts as ARCserve users and Windows passwords with it. A limited auditing will also be provided – this will tell the end user about the operations performed by ARCserve users (including login details)Password management for encrypted backups – helps the user in recovering data that is encrypted – don’t need to remember the passwords that could be changing every month.The customers will be able to submit backups with the option of ARCserve remembering the password for recovery purposes – this will ease the recovery processPassword management for backup clients – ARCserve will store the user/password for all backup clients; this will help the user to submit backups and restores (especially with user profiles) without the restore operator knowing the user/password of the server (to be restored)
1. Native support for 32-bit and 64 bit platform support. This includes the x64 & IA64 bit platforms as listed in section 1.2. RMAN agent – This should use the Oracle RMAN based backup & recovery mode as was done in UNIX RMAN agent. i. The basic objecti9ve is to support everything that UNIX RMAN agent supports. ii. Some extra features “could” be considered ONLY if we have time.3. Data objects that should be considered for backup and recovery• RMAN based backup- Entire Database/Instance- Individual Tablespaces- Individual data files- Control File- Archive LogNote: Stream-based backup, Full or IncrementalJob package created by Agent, initiated by OraclePoint-in-time consistency among Tablespaces backed up in a single job is maintained by RMAN. Point-in-time consistency among Tablespaces backed up individually is maintained using the Archive Log.4. RMAN Agent should support full instance restore toi. Original Locationii. Alternate Location5. Full Cluster Environment Support - In r11.5, Oracle Agents only provide relatively limited support to the cluster environment. User can only use one node in the cluster to do backup and restore, and the data backed up by one node can only be restored by the same node. With the full cluster support, user can use multiple nodes to do backup and restore. This will significantly leverage the power of the cluster environment.6. Support ASM, Oracle Raw partitions and RAC7. Backup & recovery of duplicate databasesNote: CES 15742658 Unicode compliantOnline and offline backup and restore – r12 just can support offline mode for RMANIncremental Backup – r12 can not support incremental Backup for RMANAutomatically Recovery – r12 just can restore automatically and recovery manually for RMAN
1. Native support for 32-bit and 64 bit platform support. This includes the x64 & IA64 bit platforms as listed in section 1.2. RMAN agent – This should use the Oracle RMAN based backup & recovery mode as was done in UNIX RMAN agent. i. The basic objecti9ve is to support everything that UNIX RMAN agent supports. ii. Some extra features “could” be considered ONLY if we have time.3. Data objects that should be considered for backup and recovery• RMAN based backup- Entire Database/Instance- Individual Tablespaces- Individual data files- Control File- Archive LogNote: Stream-based backup, Full or IncrementalJob package created by Agent, initiated by OraclePoint-in-time consistency among Tablespaces backed up in a single job is maintained by RMAN. Point-in-time consistency among Tablespaces backed up individually is maintained using the Archive Log.4. RMAN Agent should support full instance restore toi. Original Locationii. Alternate Location5. Full Cluster Environment Support - In r11.5, Oracle Agents only provide relatively limited support to the cluster environment. User can only use one node in the cluster to do backup and restore, and the data backed up by one node can only be restored by the same node. With the full cluster support, user can use multiple nodes to do backup and restore. This will significantly leverage the power of the cluster environment.6. Support ASM, Oracle Raw partitions and RAC7. Backup & recovery of duplicate databasesNote: CES 15742658 Unicode compliant
1. Native support for 32-bit and 64 bit platform support. This includes the x64 & IA64 bit platforms as listed in section 1.2. RMAN agent – This should use the Oracle RMAN based backup & recovery mode as was done in UNIX RMAN agent. i. The basic objecti9ve is to support everything that UNIX RMAN agent supports. ii. Some extra features “could” be considered ONLY if we have time.3. Data objects that should be considered for backup and recovery• RMAN based backup- Entire Database/Instance- Individual Tablespaces- Individual data files- Control File- Archive LogNote: Stream-based backup, Full or IncrementalJob package created by Agent, initiated by OraclePoint-in-time consistency among Tablespaces backed up in a single job is maintained by RMAN. Point-in-time consistency among Tablespaces backed up individually is maintained using the Archive Log.4. RMAN Agent should support full instance restore toi. Original Locationii. Alternate Location5. Full Cluster Environment Support - In r11.5, Oracle Agents only provide relatively limited support to the cluster environment. User can only use one node in the cluster to do backup and restore, and the data backed up by one node can only be restored by the same node. With the full cluster support, user can use multiple nodes to do backup and restore. This will significantly leverage the power of the cluster environment.6. Support ASM, Oracle Raw partitions and RAC7. Backup & recovery of duplicate databasesNote: CES 15742658 Unicode compliantOnline and offline backup and restore – r12 just can support offline mode for RMANIncremental Backup – r12 can not support incremental Backup for RMANAutomatically Recovery – r12 just can restore automatically and recovery manually for RMAN
1. Native support for 32-bit and 64 bit platform support. This includes the x64 & IA64 bit platforms as listed in section 1.2. RMAN agent – This should use the Oracle RMAN based backup & recovery mode as was done in UNIX RMAN agent. i. The basic objecti9ve is to support everything that UNIX RMAN agent supports. ii. Some extra features “could” be considered ONLY if we have time.3. Data objects that should be considered for backup and recovery• RMAN based backup- Entire Database/Instance- Individual Tablespaces- Individual data files- Control File- Archive LogNote: Stream-based backup, Full or IncrementalJob package created by Agent, initiated by OraclePoint-in-time consistency among Tablespaces backed up in a single job is maintained by RMAN. Point-in-time consistency among Tablespaces backed up individually is maintained using the Archive Log.4. RMAN Agent should support full instance restore toi. Original Locationii. Alternate Location5. Full Cluster Environment Support - In r11.5, Oracle Agents only provide relatively limited support to the cluster environment. User can only use one node in the cluster to do backup and restore, and the data backed up by one node can only be restored by the same node. With the full cluster support, user can use multiple nodes to do backup and restore. This will significantly leverage the power of the cluster environment.6. Support ASM, Oracle Raw partitions and RAC7. Backup & recovery of duplicate databasesNote: CES 15742658 Unicode compliantOnline and offline backup and restore – r12 just can support offline mode for RMANIncremental Backup – r12 can not support incremental Backup for RMANAutomatically Recovery – r12 just can restore automatically and recovery manually for RMAN
All these options and agents are included in the file server suite, so customers are entitled to use all these components in one server and they can add or remove components in that server without worrying about costs due the fact they already paid for them.
The email, database and application server suites include everything from the file server suite plus the agents for email available in ARCserve in one single packageThis is per server
Suite contains all technologies needed to protect Microsoft, VMware or XEN virtual machines Using traditional agents or through the hypervisorIncludes Open File, MS VSS and Granular Restore CapabilityOne license needed for each guest and proxy serverHypervisor license is "FREE" with guestsLicensing not impacted by "HOW" backup is performedNetwork based backup and VCB based backup will need same number of licensesLicense needed even if “AGENT IS NOT INSTALLED” inside guest
With release 12 dot 5, we added replication and high availability for Microsoft SharePoint servers that are deployed in all-in-one server configuration. Of course this means that your customers’ IT administrators may use CA XOsoft Assured Recovery for their SharePoint DR testing too.
In release 12 dot 5, you or your customers’ IT administrators may now protect the server that hosts the CA XOsoft Control Service itself. Before 12 dot 5, replication scenarios already defined would not be affected, but IT administrators would not be able to control, manage and monitor the replication scenario’s state. Nor could they create new replication scenarios.This new control service high availability feature eliminates these potential issues.
Release 12 dot 5 provides independent Replication and High Availability of multiple guest operating systems and applications running on a MS Hyper-V Server to another Hyper-V server, without having to install the CA XOsoft on each of the guest operating systems. This features helps speed CA XOsoft deployment and improves your customers’ IT productivity while lowering deployment costs.