In the world of Business-Critical Applications, especially IO intensive Oracle workloads, there is always a need for storage migration, based on the ever-demanding workload profile. For example,
- Migrate storage from one Tier to another Tier within a storage array
- Migrate storage from one array to another array (within a datacenter and even between datacenters as part of DC relocation)
This approach is independent of whether those workloads are virtualized or not. The end goal is to ensure that the underlying storage architecture can provide and sustain the demanding needs of the Application.
This article describes how storage migration can be performed for Oracle database running on VMware vSphere, for any types of underlying storage. The migration is done using a combination of two key technologies depending on the database deployment model
- VMware Storage vMotion
- Oracle Automatic Storage Management (ASM).
Before describing this technique, we first review some key ideas, including the deployment model of Oracle on vSphere and the fundamentals of Storage vMotion.
This blog focuses on Storage vMotion of Oracle Non-RAC workloads within the same vSphere Cluster.
Continue reading







You must be logged in to post a comment.