An important component of the backup process is the backup Agent that resides on the application host to send data over the LAN to the backup server. This method of data copy has multiple drawbacks, including performance impact on production systems and slow backup performance due to the bandwidth that we will be discussing later during this presentation.But mainly, the increasing amount of digital data and the global nature of our economies are exercising additional pressures on the ever shrinking backup window, which is the interval of time where the load on production servers is minimal and the backup process can take place without affecting production environments or ongoing business processes. This typically takes place after business hours.This daily tape backup process also creates a lot of complexity when it comes to managing multiple tapes and the retention schedules or the rotation of those tapes. This process is error prone and strains a lot of resources and time.Another challenge is the fact that it’s hard to verify the validity of the backup job unless you remount the tape to check the integrity of the data on it. The resource requirements for this verification mean that it tends to be performed only rarely.The last challenge is the recovery process and the extended time of the recovery itself, as well as the recovery point objective attached to tape backups or backups in general. It is very common to see recovery times extending beyond 24 hours and recovery points from at least the last day’s backup.
What else can we do to protect data? There are a number of things we can do at the storage level to increase data protection.
This diagram maps out the different components of the solution so far. Next we’ll look into specifics of how it works. At the top of the diagram, we see that ASD installs into the VMware Service Console on the ESX server. Under that we have individual virtual machines. Within those machines there are two agents. One, if needed, is the application-specific snapshot agent, for applications such as Exchange, SQL, Oracle, DB2, etc. This Agent makes sure the application is put into a backup mode and transactions are written to disk. Also in the VM is a file system agent, for Windows or Linux File system. This is needed to make sure the file system level is also in a backup mode and transactions are flushed out of cache. Everything needs to be stable on the disk before the snapshot is made. At the bottom is FalconStor CDP, which provides the online backup repository for ESX.
This slide outlines the steps involved in the taking the snapshot. The snapshot request is initiated from CDP. This is normally a scheduled process, but it can be manually activated as well. The Application Snapshot Director receives the request and then informs the application snapshot agent running within the virtualized application to put the application into a backup mode. Once the application is in backup mode, the file system is notified in order to flush out any data that may still be in cache or in transit. When the VM is fully in backup mode, the next request goes to the ESX server which uses VMware snapshot technology to place the full ESX sever into a backup mode. At this point, the entire system is static, all transactions written to the backup disk The fourth step is to take the snapshot at the storage level. This entire process takes only a few seconds. It takes long to explain it than it does to happen.After the snapshot is done, all systems are released and go back to normal mode. A key benefit of this method is that the VMware snapshot is used only for a few seconds, rather than for the length of the backup process. Recall what we said earlier about the impact of VMware snapshots. The FalconStor method greatly reduces this impact.
FalconStor provides a Storage Replication Adapter, which is an integration tool for integrating with VMware Site Recovery Manager. This is not the place for a full discussion of SRM, but we highly recommend taking a look at SRM as it is a very good tool for managing the replication process. SRM is a management tool. It does not move data. FalconStor CDP provides the actual data movement, coordinated with SRM. A very good feature of SRM is the ability to run disaster recovery scenarios. You can test your DR setup to make sure that applications will start as expected. All this is done without breaking the replication process.
This diagram combines all the pieces we have seen. The top portion is the only new piece. Here we see how the FalconStor SRA installs along with SRM in the VMware Virtual Center (a separate system).
FalconStor NSS uses patented MicroScan replication. This is the most efficient replication model on the market, because it is the most efficient possible form of replication. When applications or file systems write data, they often write far more data than actually changes. For example, a file system may write 8k of data at a minimum, no matter how much data actually changes. In other words, the same content is often re-written to the same storage sectors. Many replication tools will copy all the data that changes. In this illustration, the colored blocks show a typical 8k write by a file system. However, within that 8k of data, only a few sectors may actually change, as shown by the blue squares. NSS scans the disk at the 512 byte level to identify the sectors with NEW data and it copies ONLY those sectors over the network. This can dramatically reduce the amount of data being replicated.
This slide show some real world data from an Exchange environment. It consists of 1300 Exchange users across four storage groups. The data is replicated hourly from California to Pennsylvania. Microscan is particularly effective with Exchange because of the random-write nature of Exchange data. If you look at the chart, in the second column we see the amount of data changes accumulated by Exchange, as measure at the application level. The next column shows those same sectors after being filtered by MicroScan. On average, Microscan replicated only between 2 and 3% of the total data change recorded, because that represented the actual NEW data. Overall, WAN traffic was reduced by 97%. Not all applications will have quite this level of WAN reduction. It does depend on the nature of the application and how it writes data. But typically, we see reductions on the order of 80-90% or more.
Agenda<br /><ul><li>Data Protection in VMware Environments</li></ul>Data Protection demonstration<br /><ul><li>Data integrity and system recovery
Backup, Disaster Recovery, and Site Recovery Manager</li></ul>Site Recovery Manager demonstration<br />Physical to Virtual support with Site Recovery Manager<br /><ul><li>WAN optimization</li></li></ul><li>Data Protection for Virtual Environments<br />
The True Value<br />Lies in the Heart of the Enterprise<br />
Efficient Data Management is Mission Critical<br />Operating Systems may change and evolve<br />Application vendors may come and go<br />Servers are being virtualized and democratized<br />Data is persistent and the immutable and ever-present corporate asset<br />Data is the Vital Center <br />
Enhancing Data Protection<br />What can we do to enhance data protection?<br />
VMware Recovery with FalconStor Software<br /><ul><li>FalconStor software provides a set of tools to enhance VMware data protection</li></ul>100% transactional integrity of data for fast restores <br />WAN-optimized data replication to reduce bandwidth use by 90% or more<br />Integration with VMware vCenter Site Recovery Manager <br />Physical-to-virtual support with Site Recovery Manager<br />
Application-centric Protection<br />Why is application integration important?<br />Because when you recover, you want your data to look like this<br />And not like this<br />
FalconStor Snapshot Director for VMware<br /><ul><li>FalconStor Snapshot Director for VMware is designed to ensure transactional integrity of data</li></ul>Data is not in a crash consistent state (it is 100% transactionally consistent)<br />No need for lengthy system/DB checking<br /><ul><li>Coordinates snapshot process between VMware and FalconStor application-specific and file system-specific snapshot agents
Provides reporting for proof of compliance </li></li></ul><li>Challenges for Site Recovery Manager Implementation<br /><ul><li>Site Recovery Manager does not move data by itself, it requires array-level data replication
Limited number of disk vendor certifications for Site Recovery Manager
Vendor Storage Replication Adapter (SRA) is platform specific</li></ul>Need the same hardware on both primary and remote sites<br />Limited product certifications<br /><ul><li>Need to change the underplaying infrastructure at the primary site, the secondary site, or both
Breaks the virtualization promise of platform independence</li></li></ul><li>Integration with Site Recovery Manager <br /><ul><li>FalconStor Storage Replication Adapter (SRA) integrates FalconStor replication with VMware vCenter Site Recovery Manager
Virtual disk assignments are automatically coordinated with associated virtual machines with the help of FalconStor SRA
Disaster recovery scenarios can be tested at any time</li></ul>A TimeView™ snapshot image is created and mounted to a virtual machine being tested<br />The virtual machine is started<br />Recovery is validated and the TimeView is image removed<br />
Key Components of Site Recovery Manager integration with FalconStor DR Solutions<br />VMware Virtual Center<br />FalconStor Storage Replication Adapter coordinates with Site Recovery Manager, installs in Virtual Center<br />Service Console<br />Snapshot Director<br />Virtual Machine<br />Virtual Machine<br />Virtual Machine<br />Application<br />Application<br />Application<br />Site Recovery Manager <br />Storage Replication Adapter<br />Snapshot Director<br />Application Snapshot Agent<br />Application Snapshot Agent<br />Application Snapshot Agent<br />ESX<br />Application and file system agents<br />File system Agent<br />File system Agent<br />File system Agent<br />FalconStor CDP provides replication services coordinated with Site Recovery Manager<br />FalconStor CDP<br />OS<br />OS<br />OS<br />
FalconStor Storage Virtualization Device<br /><ul><li>FalconStor CDP certified for vCenter Site Recovery Manager
Allows any storage on VMware Hardware Compatibility List (HCL) to be used with Site Recovery Manager</li></ul>In effect, FalconStor CDP extends Site Recovery Manager certification to connected disk<br /><ul><li>Increases storage array flexibility for VMware Site Recovery Manager, brings support to existing SAN
Allows Site Recovery Manager testing without breaking the replication stream</li></li></ul><li>Heterogeneous SAN Replication Any-to-Any Disk – Freedom from Vendor Lock-in<br />
Heterogeneous Replication – Any to Any Disk<br />Primary Site<br />Remote Site<br />Management<br />data<br />VMware vCenter Server with Site Recovery Manager<br />VMware vCenter Server with Site Recovery Manager<br />VMware<br />ESX <br />Server<br />VMware<br />ESX <br />Server<br />VMware<br />ESX <br />Server<br />VMware<br />ESX <br />Server<br />Heterogeneous Replication<br />With Auto-failback Support<br />Any storage<br />Disk Vendor B<br />Any storage<br />Disk Vendor A<br />
Achieving Efficient Data Replication<br />Deploy sub-block replication to move your data<br />
MicroScan™ WAN optimization<br />512 byte<br />= empty disk sector<br /><ul><li>Applications and file systems write far more data to disk than actual changes
FalconStor CDP scans the changes at a 512 byte level and replicates only the changed data</li></ul>Avoids constant re-sending of duplicate data<br />= data written by application or file system<br />= sector with actual data change<br />512 byte<br />Disk sectors<br />A typical 8k write of data. Many systems send all 8k or more. FalconStor CDP sends only the truly changed sectors. <br />
MicroScan WAN Savings Example<br /><ul><li>Actual user production data for Microsoft Exchange replication</li></ul>1300 users, hourly replication from CA to PA<br />High random-write nature of Exchange is well suited to MicroScan removal of duplicate data<br /><ul><li>Average WAN traffic reduction of 97% with no additional network equipment needed</li></li></ul><li>Solution Deployment Options<br /><ul><li>All FalconStor solutions are available in three forms</li></ul>CDP<br />Gateway Appliance or Software Kit<br />Virtual Appliance<br />Storage Appliance<br /><ul><li>Server+storage in a single physical device