HPE GreenLake for Disaster Recovery makes life a lot easier because it is a single all-in-one solution. It is easy to set up and configure, and with that testing functionality integrated, it also gives me that ease of mind because I know that it my DR procedures effectively works. Previously, the testing procedure with other tools took me several hours, even days, to be sure, and now, I can test in a matter of minutes. I know that everything is okay or not. If there is a disruption in my environment, I just have to go into the UI from Disaster Recovery, and it tells me what my RPO is effectively at that moment, which is somewhere between five and ten seconds. That is it. Recovery is very easy because I can see directly what is going wrong and which server or site is down under the integrated failover testing. I can do an effective failover, so I do not even have to go on-site. I can do it from anywhere. I can initiate a failover in case of a disaster to my DR server. HPE GreenLake for Disaster Recovery provides a single SaaS control console for multi-site management. It works, and I use it. This single portal or the single pane of glass gives me access to all my gear. It now also gives me all the services. It gives me all the applications and software that I am running on top of the gear. I use it quite often. I am able to manage compute and storage, as well as DR, from a single console. For me, it is very important because until now I had to use multiple consoles and multiple applications to have the big picture of all my data with all the hardware underneath it. Now, I have that single pane of glass from where I can see everything at the same time. It simplifies my life a lot. HPE GreenLake for Disaster Recovery enables me to protect our data with no scheduling, snapshots, or agents to be installed. It simplifies my life a lot because it is easy to use, and we do not need to use all those integrations between different solutions. Its unique journaling capabilities enable me to recover data from a large number of checkpoints that are seconds apart. I already tried it, and it is a part of my testing procedure. I tried to recover from multiple checkpoints, and that effectively worked. I have checkpoints for up to two days if I remember well, and until now, it all works fine. Our Recovery Point Objectives went from days and hours to seconds. The most impressive thing about this solution is that I can now very easily specify that these mission-critical VMs are protected with Disaster Recovery, and these non-mission-critical VMs are protected with Backup and Recovery, which is a data protection tool from GreenLake, so I am using both of them.
