Migrate Workloads to Power Virtual Server - IBM Power Virtual Server
Migrate Workloads to Power Virtual Server - IBM Power Virtual Server
“POWERVS2000” at checkout.
To learn more about IBM Power Virtual Server, visit our product page
Migrate to hybrid cloud: Grow at your own pace: Run mission-critical workloads: Work For any questions, and more information, contact
Seamlessly move and manage Extend workloads and take on nonproduction tasks and
your workloads across cloud
and on-premises environments.
advantage of pay-as-you-
use billing to manage costs.
production environments
simultaneously. Use VMs to help
Mark Martin, Product Manager,
resolve issues faster.
IBM Power Virtual Server, by email at
Modernize Power Optimize consumption: Add capacity to your
[email protected].
workloads: Connect to Power infrastructure on demand within minutes.
services to transform Manage on premises or off premises. * New clients need to deploy PowerVS QuickStart to be eligible for PowerVS2000 credits. Credits apply to virtual server instances deployed in non-US
business models. datacenters. Promo offers valid for signup while supplies last. Offers cannot be combined with any other promos or offers. Valid onnew orders only.
This documentis forinformationalpurposesonly. Allinformationprovidedhereinis subjectto change withoutnotice.
Pleaserefer to the specific contracts for details; this is a summary, and the applicable contract provides the binding obligations betweenthe parties. If thereis a discrepancy
betweena contractandthisguidance,thecontractwillprevail.
Migration Considerations
• Client Modernization Initiatives (e.g. update O.S. version, app modernization, etc.)
• For larger data size, transfer directly to PowerVS over the network, if possible
• Combine Backup/Restore(for seeding) and Replication options (to synchronize or catch up) in a no-
downtime environment
• Create ova formatted images and transfer via COS to quickly create PowerVS LPAR with ova image,
for LPAR < 2TB with access to PowerVC
IBM i Migration Recommendations
• Use Backup and Restore as the most common approach to migration
• OS level (SAVSYS, Save 21,23,24)
• Application (SAVLIB, SAVOBJ)
• For smaller data size, transfer directly to PowerVS over the network, if possible
• Prefer Direct Link over IPSEC VPN and internet where feasible
• Transfer via COS (BRMS/ICC) may be acceptable for partition < 2TB
• For larger data sets, leverage FalconStor Storsafe VTL to deduplicate and minimize data transfer to
the cloud
• Combine Backup/Restore (for seeding) and Replication options (to synchronize or catch up) in a
no-downtime environment
• Create ova formatted images and transfer via COS to quickly create PowerVS partition with ova
image, for partition < 2TB with access to PowerVC
Different scenarios and Power Virtual Server migration scenarios:
options possible
<2TB >2TB
7
Getting data to the cloud
8
Workload dependent solution - Oracle
Oracle based solution:
IBM Power Virtual Server
• Use Oracle Technical Migration procedure
9
Migrate Oracle workload to
IBM Power Virtual Server
11
Migrate Db2 on AIX workload
to IBM Power Virtual Server
https://cloud.ibm.com/docs/sap?topic=sap-sapmig-db-oracle
Workload dependent solution – Db2 SAP ECC on Oracle
IBM Power Virtual Server • Use SAP ECC on Oracle Technical Migration procedure
13
Migrate SAP ECC AIX IBM Cloud Docs
https://cloud.ibm.com/media/docs/downloads/powe
r-iaas/db2_migration.pdf
Manual saves and migration with
MKSYSB and FTP
AIX Solution:
IBM Power Virtual Server
• Manual saves with MKSYSB command and FTP
If you want to migrate your current AIX • Use native AIX MKSYSB command to save to local
environment to IBM Power Virtual storage and use FTP to get the save data off the
Server using standard AIX commands. system
• OS save only
15
Use MKSYSB to migrate
17
IBM PowerHA GLVM
18
Migrate to the cloud
IBM i Solutions
IBM Power Virtual Server • Manual saves to virtual tape and FTP
or
19
Manual saves to virtual tape and FTP
IBM i solution:
IBM Power Virtual Server • Manual saves to virtual tape and FTP
20
Use Native IBM i Tools
BRMS/ICC IBM i solution:
• BRMS/ICC for <=2TB
IBM Power Virtual Server • The Backup Recovery and Media Services (BRMS,
5770-BR1 or BR2) and Cloud Storage Solutions
(5733-ICC) LPPs are available to purchase as non-
For Migration requiring 2TB or less, you expiring or 90-day/1/2/3/4/5-year subscription term
can rely on BRMS when combined with options
ICC as your more automated backup to • The new 90-day subscription term options are ideal
cloud solution. for migration to Power Virtual Server
This gets data into Cloud Object Storage (COS) which then can used
to retore the data in a new created Power Virtual Server Instance
(VSI). Cloud Object Storage is available in the IBM Cloud Catalog.
22
Use ICC to create additional off-premises copies
• BRMS automatically
duplicates tapes to IBM
Cloud Object Storage
(COS)
• Capable of restoring in
Power Virtual Server as
a clean room as part of
a cyber resiliency
strategy
BRMS with ICC
• Backup process is not finished until the data is moved off the
• Backup Recovery and Media Services (BRMS, 5770-
box
BR1 or BR2) and Cloud Storage Solutions (5733-ICC)
LPPs
• Partition/storage size is limited, to fit the process in the backup
window
• Additional storage required to save local first
• Compression can be utilized to reduce network transfer
• Compression is now supported which saves
time
~50% of the local storage requirements
• Full System restore requires a network install server
BRMS with ICC
IBM Cloud
Object Storage
https://cloud.ibm.com/media/docs/downloads/powe
r-iaas/IBMi_BRMS_ICC.pdf
Migrate While Active IBM i Solution:
IBM i Migrate While Active is now available
IBM Power Virtual Server Easily migrate from on premise to PowerVS
https://www.ibm.com/support/pages/ibm-i-migrate-while-active
27
IBM i Migrate While Active – How it Works
Step 1: Initial System Save Step 2: Transfer SAVE to PowerVS Step 3: Transfer Changed Data
Network Install
On Prem On Prem Target Copy Server
Pattern 1. Using IBM i Local Storage Server (PowerVS)
Network install of
2 Copy Node Transfer the changed data that has occurred since completion of
BASE SYS SAVE the initial SAVE.
– OPT IMGCLG
DATA SAVE
– TAPE IMGCLG
3
Transfer and Target Copy Server
restore of Data (PowerVS)
Network Install
Pattern 2. Use VTL for DATA SAVE On Prem Server (PowerVS)
2
BASE SYS SAVE Network install
– OPT IMGCLG of Copy Node
DATA SAVE
28
Simply visit the IBM Cloud Catalog and search for FalconStor VTL
You can download the on-premises license and subscribe to the VTL Cloud
capability. Be sure to look at their deployment guide found in the Docs area.
Take advantage of FalconStor’s Deduplication technology to reduce your
repository in cloud.
For migration to cloud requiring >2TB, simply add FalconStor VTL
to your BRMS implementation and scale to sizes in tens/hundreds Also works with DSI VTL on-premise devices
29
of TBs or PBs if needed.
VTL Solutions with IBM i
PowerHA Solutions
• For customers with existing HA/DR solutions such as
IBM PowerHA geo mirror and ISV logical replication
solutions, Power Virtual Server can be setup as a
If you need Migration options, you can
target
count on IBM and Power Virtual Server to
meet your requirements. IBM has Migration • For customers in Power Virtual Server, PowerHA is a
solutions available. selectable option
31
DR and HA Applications
32
IBM PowerHA Geo Mirroring
33
DR and HA Applications
34
Different scenarios and More information around Power Virtual
options possible
Server migration scenarios can be found
in the Cloud Docs:
• Manual and automated
options
• Workload depended
https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-system-migration
35