Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article shows how to move your Oracle workload from your on-premises environment to the Oracle Database@Azure. A proven discovery, design, and deployment approach are recommended for the overall migration strategy, followed by data migration, and cut over.
Discovery
Migration begins with a detailed assessment of the Oracle product portfolio and applications involved. The existing Oracle database can operate Oracle Real Application Clusters (RAC). For applications, we need to discover the size of the infrastructure that can be done easily by using Azure Migrate based discovery. For the database sizing ask your Oracle Sales Representative for advice.
Design
For Applications, Azure Migrate do lift and shift infrastructure and applications to Azure IaaS based on discovery. The solution must have high reliability and resilience in the occurrence of disasters, as determined by the parameters of Recovery Point Objective (RPO) and Recovery Time Objective (RTO). Oracle landing zone offers architecture guidance to choose the best solution architecture based on RPO and RTO requirements.
Types for data migration 
The data migration process distinct between physical and logical migration. The logical migration is a method for migrating databases where data and schemas are extracted, transformed, and loaded into the target database. It is particularly useful for scenarios where you need to migrate across different architectures, database versions, or platforms. This approach includes Data Pump and GoldenGate. The physical migration involves moving the entire database as-is at the storage or datafile level from a source system to a target system. The database structure remains unchanged. It's ideal when moving to a system with the same database version and compatible architecture. Tools used for this scenario are RMAN and Data Guard. Please revisit Oracle logical online migration for further guidance.
Data migration approach
After you set up Oracle on Azure infrastructure, install Oracle database, and migrate related applications; the next step is to transfer data from on premise Oracle database to the new Oracle database on Azure. See the following Oracle tools:
Azure enhances the Oracle tools with the right network connectivity, bandwidth, and commands that are powered by the following Azure capabilities for data migration.
- VPN Connectivity
- Express Route. Reliability of the ExpressRoute is the key. Refer to resiliency guidance for Gateway and Circuits.
- AzCopy
- Data Box
Oracle tools for data migration
To migrate, there are various options available. The following diagrams provide an overview of these.
You need one of the Oracle Tools plus Azure infrastructures to deploy the correct solution architecture to migrate data. See the following reference solution scenarios:
Scenario-1: ZDM: Use Zero Downtime Migration, which can be a logical or physical migration based upon your Database version, operating systems and downtime requirements. This setup leverages Data Guard in a logical migration.
Scenario-2: RMAN: Use RMAN backup and restore with Azure features, the setup for RMAN based recovery. The main thing is the network between on-premises and Azure.
Scenario-3: RMAN Backup Approach with nfs mount
Note
If you plan to use a private endpoint with a Azure Blob Storage and nfs mount, please make sure to deploy a local NVA into a different subnet within the same VNet as your ODAA relies.
Scenario-4: Data Pump with Azure NetApp Files or Azure Virtual Machine with nfs mount
Note
If you plan to use a private endpoint with a Azure Blob Storage and nfs mount, please make sure to deploy a local NVA into a different subnet within the same VNet as your ODAA relies.
Scenario-5: Data Box - a unique scenario in which data is moved between the locations using a storage device and physical shipment.
Note
For planned migration which is performance sensitive, we recommend using Azure Netapp Files.
Post migration tasks
After the cutover, verify all business applications are functioning as expected to deliver business operations in tandem with on premise.
- Perform validation checks to verify data consistency and application functionality.
- Update documentation, including: network diagrams, configuration details, and disaster recovery plans.
- Implement ongoing monitoring and maintenance processes for Azure VM hosting the Oracle database.
Throughout the migration process, it's essential to communicate effectively with stakeholders, including application owners, IT operations teams, and end-users, to manage expectations and minimize disruption. Additionally, consider engaging with experienced professionals or consulting services specializing in Oracle-to-Azure migrations to ensure a smooth and successful transition.