Podcast Recap: Different Flavors of Migration on BIASed Podcast Channel

Podcast Recap: Different Flavors of Migration on BIASed Podcast Channel

Recently, our team leaders recorded a podcast discussing the many migration processes at BIAS – and why one may be preferred over another. BIAS performs these migrations across multiple platforms, including: commodity hardware to engineered systems, distributive systems to Oracle’s OCI Cloud, Mainframe to Oracle and other cross-platform migrations.

The techniques used at BIAS apply to both on-premise and cloud migrations. Anyone can start a migration, but BIAS has the in-house experience to make it happen using industry best-practices and proven methodology. Our experienced team and our precision toolkit combine for a tried-and-true system with proven results perfected over time.

BIAS has perfected our custom tool kit over 7,000 migrations and utilizes the following methods:

● RMAN cloning

● Import/Export using Oracle Datapump

● GoldenGate

● +ASM Diskgroup Sync

● Cross-platform Transportable Tablespace with Incremental backup

Here are some key highlights covered in our Migration Factory Podcast “Different Flavors of Migration”:

Recent Recommendation: RMAN Cloning

After highlighting the migration types, Co-Founder and Executive Vice President, John Ezzell, asked Mark Saltzman, Senior Director of Database Services at BIAS, to discuss the appropriate scenarios for RMAN cloning, a type of migration the team has been using more frequently as of late:

“For a long period of time, I felt that datapump was the easiest and best way to do migrations. Recently, I’ve changed my thinking and prefer using the RMAN cloning method. A majority of Oracle databases recently are now centered around Linux Operating Systems rather than Solaris or AIX making RMAN an easy choice.

A lot of the migrations we’ve been doing recently are centered around hardware refreshes. RMAN cloning comes into play since it’s quick and it gives us the flexibility to quickly migrate from a legacy server to a new server.”

Why Migrate?

Why would a company leave one environment to migrate to another?

As Mark explains, it’s often about the need for a tech refresh. For example, a BIAS customer wanted to move from an X5 Oracle Database Appliance (ODA) to an X7 ODA. Migration experience is at the core of those changes regardless of the vendor or version.

BIAS Core Technologies Vice President, Doug Rhoades, took listeners through another example of a migration performed for a healthcare distributor. This customer was migrating their E-Business suite system to Oracle’s Infrastructure as a Service Cloud and Platform as a Service Cloud, and the team used the RMAN cloning method.

RMAN was used because the customer’s data was on a third-party host, and this method required the least amount of interaction to get the data moved over for a faster, less complex migration. RMAN also allows data-at-rest encryption during the migration process, which is another example of an advantage this method brings.

A Team-Favorite Method

One of Mark’s favorite techniques is Import/Export leveraging Oracle datapump. Using international businesses as an example, he explains that the Import/Export migration allows for a more diverse conversion. With RMAN cloning, migrations are a like-to-like, single format conversion, whereas Import/Export allows for different features such as multi-bit European or Chinese character sets.

Supporting files, tables and documents with characters that might not be recognized with the older format means less time in post-migration conversion – a conversion that builds native support on the go, essentially.

Cross-platform moves such as Solaris or AIX to Linux are often necessary when businesses want new or better features with a different vendor. As Mark explains, leveraging GoldenGate during an Import/Export ensures this move happens more smoothly:

“You can leverage GoldenGate or you can leverage cross-platform transportable tablespace. If you’re going to do it, you might as well use GoldenGate, in my opinion — unless there are a lot of objects that are not supported by GoldenGate, like in an E-Business suite environment.

 

Many years ago, I migrated an 11.1 database to 12.1 leveraging GoldenGate and it was from Solaris to Linux. What we ended up doing was a restore from backup to a standby server.

We started GoldenGate prior to that on the production environment, and then started the export on the standalone database. Over the course of a week, we rebuilt this 40-terabyte database on a Linux platform, upgraded it to 12.1 (the target database version), started up GoldenGate, and brought it into sync.

This method allowed us reset all of the high watermarks, which decreased the storage footprint.”

The client saved critical hours for their hotel engagement system. Every hour of outage would have cost the company $4 million in revenue, but an agile and efficient migration minimized downtime and saved money during the cut-over.


The techniques used in that migration and many more have been applied and practiced numerous times by the BIAS team. With an average of 10+ years of experience among our consultants, BIAS has the expertise to guide customers across the Commercial and Public sectors through their data migrations – regardless of the type of migration chosen.

To listen to “Different Flavors of Migration” podcast in its entirety, please click the link below:

Recommended Podcast Graphic_Different Flavors of Migration

Legal

The following thoughts, intentions, strategies and/or solutions are those of the blog authors and do not represent the position of anyone other than the authors.