StandbyMP will revolutionize how organizations manage DR enterprise-wide by making the same Gold Standard of DR available to both Oracle SE and MS SQL Server users - all from a single common user interface.
Every cloud needs Disaster Recovery
No cloud is immune to downtime, and most people are less protected than they think. As part of your cloud migration, it is essential to deploy Disaster Recovery that meets your RTO/RPO needs.
StandbyMP software for the cloud guarantees database continuity with a continually verified standby database that is always available and ready to take over at a moment's notice.
Dispelling the common cloud myths
"I'm in the cloud so I don't need Disaster Recovery"
Cloud infrastructure providers typically don't include resilient Disaster Recovery. Instead, they recommend you implement out-of-region DR for business-critical databases.
"Clouds are more reliable than on-premise"
Moving to a Cloud Service Provider (CSP) doesn’t magically fix availability problems. The cloud is also vulnerable to downtime, accessibility issues, and performance problems.
"I'm safe because I have in-region high availability"
It is not uncommon for entire regions to go down. Multi-region replication is recommended by CSPs but can be difficult to implement for databases without the help of specialist software.
"My data is protected because I have backups"
While backups are a necessary part of any Disaster Recovery plan, traditional backups no longer meet the data loss (RPO) and recovery speed (RTO) requirements of most businesses. Backups are also difficult to test and vulnerable to corruption.
What approach is recommended by Cloud Service Providers (CSPs)?
When looking at database availability in the cloud, CSPs such as Amazon and Oracle recommend out-of-region replication as the basis of best-practice Disaster Recovery. Organizations then match the type of replication to their RTO and RPO requirements.
As evidenced by Amazon's six-hour regional failure in 2021, in-region high availability is not enough by itself. A resilient warm standby database is the cornerstone of best practice Disaster Recovery.
Key considerations when migrating to the cloud
Learn what Cloud Service Providers (and Dbvisit) recommend to ensure Database Continuity.
- Common cloud myths and why we need to dispel them.
- Best practice approaches from Cloud Service Providers for Oracle and SQL Server.
- How to evaluate your RPO/RTO requirement.
- The difference between in-region High Availability and our-of-region Disaster Recovery.
- How to quickly implement great DR for on-premise databases using a hybrid DR approach.
Easily implement best practice DR with Standby MultiPlatform
Standby MultiPlatform allows you to quickly, easily and cost-effectively implement resilient Disaster Recovery in the cloud for your Oracle and Microsoft SQL Server databases.
Cloud DR For Oracle SE
Cloud DR For SQL Server
Cloud DR For Oracle SE
Cloud DR For SQL Server
Like Oracle Data Guard, StandbyMP uses physical replication technology to create a standby database that is continuously updated, verified and available for failover at anytime.
- Eliminate risk with a resilient and remote standby database that can meet RTO and RPO requirements across all disasters.
- Simplify DR with auto failover, one-click resynchronization, and DR testing.
- Facilitate patching and testing with zero data loss planned switchovers.
- Full Oracle technology support.
Go beyond Availability Groups and Log Shipping with StandbyMP - the Gold Standard for Disaster Recovery.
Meet your RTO/RPO requirements with a continuously verified standby database that is always available and ready to take over at the moment you need it.
- Remove complexity and risk by managing your Disaster Recovery from one central console.
- Speed up with multi database actions, guided workflows, and one-click actions.
- Simplify with intelligent standby creation, automated failover, and user replication.
- Facilitate patching and testing with zero-data-loss planned switchovers, read-only access and more.
Standby's benefits for the cloud
Remote standby creation
Implement out of region standby databases to guarantee availability
Transaction level awareness prevents corruption of the standby
Easily perform 'Graceful Switchovers' to facilitate patching or testing
Simplify workflows to speed up and reduce risk of manual errors
- Automation of configuration and management to reduce risk of manual errors
- Database aware - continual verification of standby database, to guarantee recovery
- Enable regular DR testing to validate end-to-end DR process and guarantee readiness
- Utilize Graceful Switchovers for more frequent patching and updates
Realtime and Smart monitoring simplify management and administration
How StandbyMP works
A simple architecture consists of one primary database and one standby database. The standby database is continuously updated, warm and ready to take over.
Creation: An intelligent process efficiently creates one or more standby databases in the cloud (remote region).
Synchronization: StandbyMP synchronizes the databases by compressing, sending, and applying archive logs to the standby(s). Frequency of log transmission is configurable to meet your RPO objectives and hardware constraints.
Monitoring: Real-time monitoring identifies exceptions and sends alert notifications.
Failover: Failover can be initiated automatically or with a single click. Database failover completes within a few minutes.
Standby MultiPlatform overview
Enterprise-class Disaster Recovery for Oracle SE and Microsoft SQL Server that prioritizes database integrity, disaster resiliency, recovery speed, and ease of use. All from a single common user interface. Available on-premise, in the cloud, or as a hybrid.
In-depth feature sheet
A technical description of all key features within the Dbvisit StandbyMP.
When it comes to your data, the cloud is not immune to disasters and many are not as protected as they believe. Backups and High Availability zones alone are not enough to protect your critical databases. Read on to see what Cloud Service Providers (and Dbvisit) recommend to ensure Database Continuity.