Today EMC has released more information about something shown at EMC World called EMC ProtectPoint. This new data protection offering brings direct backup from the VMAX3 to DataDomain. In today’s work when a backup is kicked started data has to slow from the storage array to the application server. This data then flows to the backup servers before being written to its final backup target. Wouldn’t it be nice to cut out this middle man and write directly from the VMAX to DataDomain? EMC ProtectPoint does just that. This new offering will have native support for Oracle at GA, but I’m expecting this to grow quickly. This will allow an Oracle DBA to use an RMAN directed backup to provide an extremely rapid and non-impactful backup. The database will be put into hot backup mode. Once complete, the VMAX data services layer will create SnapVX copies of the data LUNs. After that completed the DB is taken out of hot backup mode and snaps are taken of Redo logs. The last and final step creates a backup of all the SnapVX data directly on DataDomain. The nature of VMAX SnapVX will ensure that the snap is a differential only, which means the backup time for an entire database will be very, very quick. Even when it is running the VMAX will ensure the application data access meets its defined Service Level objectives. Recoverability is very easy as well, but does have one limitation. This backed up data on DataDomain can only be read by a VMAX array. It doesn’t have to be the same VMAX, but it must be a VMAX. As EMC ProtectPoint mature I’m expecting it to come to other EMC storage arrays. In the meantime the performance implications of this are pretty awesome to your Oracle databases.
Redefining Oracle Backup with EMC ProtectPoint
Comments are closed, but trackbacks and pingbacks are open.