If there is a data leak, incident, or compliance issue, auditors may want to verify whether there is a policy and plan in place for utilizing AWS Elastic Disaster Recovery. As part of a strategic approach, I have been part of a team ensuring compliance with various regulations, including HIPAA compliance. I have contributed to developing strategies to satisfy audits and inspections from various government bodies. These strategies outline the plans and features to be utilized if needed.
The primary use case for AWS Elastic Disaster Recovery is to ensure data replication and protection across diverse environments without the need for hypervisor integration.
AWS Solution Engineer at a tech services company with 51-200 employees
Real User
Top 20
2023-04-11T20:48:45Z
Apr 11, 2023
I've used the solution for migrations. I worked for a company that went Chapter 13, and we had to migrate into the cloud. I've used it for disaster recovery as well.
My purpose for utilizing CloudEndure Disaster Recovery is to streamline our disaster recovery procedure. In the event of any issue arising in our on-premise infrastructure, we aim to quickly switch over to AWS. Our setup is designed to facilitate this process, and we frequently conduct tests to ensure its reliability. While we have yet to experience an actual disaster, we conduct multiple tests annually. Furthermore, as a partner, I implement this solution for our clients. Currently, we have five customers using it, with the number steadily increasing. We have the solution deployed on-premise located on the Amazon AWS infrastructure.
Lead DBA at a computer software company with 501-1,000 employees
MSP
2022-05-12T02:06:09Z
May 12, 2022
For the CloudEndure DR, I have been using this for Oracle E-Business Suite and Oracle OBIEE. I've used it for the operating system and directory services as well.
Cloud Consultant at sonata information Technology Limited
Real User
2022-04-28T14:51:56Z
Apr 28, 2022
We use CloudEndure Disaster Recovery for backing up our data and for recovery. My customers have some databases. They were looking for the DR solution. CloudEndure is easy, and block-level replication will happen. Whenever my primary site goes down, the DR site will be up, and the data will be there. The DR data is there, and it will be a replication back will be my primary site.
I am a solution architect and I analyze customer's information in order to suggest products for them. CloudEndure Disaster Recovery is one of the solutions that I am familiar with. It is used for backup and restore operations.
The entire company uses it for reports we are sent to research. We also have reports that we write for various clients and it helps us look for our research requirements. All of the data and information is stored on the cloud. There were a few instances in which the entire system got hacked. There was an issue with the system, the hard drive, so we used the cloud backup to retrieve all the information from three to four years down the line.
Data backup involves copying and moving data from its primary location to a secondary location from which it can later be retrieved in case the primary data storage location experiences some kind of failure or disaster.
If there is a data leak, incident, or compliance issue, auditors may want to verify whether there is a policy and plan in place for utilizing AWS Elastic Disaster Recovery. As part of a strategic approach, I have been part of a team ensuring compliance with various regulations, including HIPAA compliance. I have contributed to developing strategies to satisfy audits and inspections from various government bodies. These strategies outline the plans and features to be utilized if needed.
The primary use case for AWS Elastic Disaster Recovery is to ensure data replication and protection across diverse environments without the need for hypervisor integration.
We are using AWS Elastic Disaster Recovery for backup purposes in our company.
We were using CloudEndure Disaster Recovery as a backup for websites when we had a double ISP outage.
I've used the solution for migrations. I worked for a company that went Chapter 13, and we had to migrate into the cloud. I've used it for disaster recovery as well.
My purpose for utilizing CloudEndure Disaster Recovery is to streamline our disaster recovery procedure. In the event of any issue arising in our on-premise infrastructure, we aim to quickly switch over to AWS. Our setup is designed to facilitate this process, and we frequently conduct tests to ensure its reliability. While we have yet to experience an actual disaster, we conduct multiple tests annually. Furthermore, as a partner, I implement this solution for our clients. Currently, we have five customers using it, with the number steadily increasing. We have the solution deployed on-premise located on the Amazon AWS infrastructure.
For the CloudEndure DR, I have been using this for Oracle E-Business Suite and Oracle OBIEE. I've used it for the operating system and directory services as well.
We use CloudEndure Disaster Recovery for backing up our data and for recovery. My customers have some databases. They were looking for the DR solution. CloudEndure is easy, and block-level replication will happen. Whenever my primary site goes down, the DR site will be up, and the data will be there. The DR data is there, and it will be a replication back will be my primary site.
I am a solution architect and I analyze customer's information in order to suggest products for them. CloudEndure Disaster Recovery is one of the solutions that I am familiar with. It is used for backup and restore operations.
The entire company uses it for reports we are sent to research. We also have reports that we write for various clients and it helps us look for our research requirements. All of the data and information is stored on the cloud. There were a few instances in which the entire system got hacked. There was an issue with the system, the hard drive, so we used the cloud backup to retrieve all the information from three to four years down the line.
Enterprise disaster recovery.