IBM i and Backups when moving to the Cloud: 'U Can't Touch This'

In today's tech landscape, some companies are riding the cloud wave, while others remain hesitant.

Traditionally, backups were physical, but times have evolved, introducing Virtual Tape Libraries (VTLs), network-based software, SAS, iSCSI, and Fibre Channel connections.

Transitioning to the Cloud: What Changes?

When discussing the intangible nature of the cloud, it's clear that we leave behind the era of physical connections like SAS, SCSI, and Fibre Channel. Instead, our primary options for cloud backups include:

1. Backup to Disk, then to a Remote Repository: Utilize NAS, File Servers, or Object Storage.
2. Backup to an IP Address using Software: Leverage cloud-based backup software.
3. Backup to iSCSI using iSCSI VTL: Emulate traditional backup methods in a virtual or cloud environment.

Which Backup Solution is Right for You?

There's no one-size-fits-all solution—only the best fit for your needs.

Backup-to-Disk-to-Cloud:

• Ideal for quick, straightforward data backups with easy configuration.
• IBM BRMS+ICC for cloud instances.
• Custom CL or BASH scripting can do the work.
• Requires additional storage for the backup.
• Save Files and Image Catalogs as local formats before cloud upload.
• Tools like S3CMD and AWS CLI ease data transfers to/from S3 Cloud Storage.
• Recommended for backups under 2TB-5TB to avoid long backup processes.

Cloud Backup Software:

• Perfect for consolidated data repositories.
• I2C, ArcServe, Carbonite eVault, or Commvault...
• Backup to remote NFS Optical Image Catalogs.

iSCSI VTL:

• Best for large data volumes.
• Emulates traditional tape libraries and cartridges.
• Supports IBM BRMS and SAVLIB commands.
• Capable of running GO SAVE menu options 21, 22, 23 .

Snapshots and Exports:

• Snapshots are excellent for change-management checkpoints.
• Exports are ideal for VM cloning and an alternative to option 21.
• Both have limitations: storage capacity, parallelism, and processing time.
• Require database quiescence (consider CHGASPACT before execution).
• Both are scriptable for automation.

Is This Good or Bad?

These options aren't inherently good or bad—they're just the diverse choices available in the cloud.

Your decision will hinge on maintaining your backup policies, backup process complexity, or saving money, based on your priorities.

Want to Learn More?

Feel free to leave a comment or send me a direct message.

Let's discuss how IBM Power Virtual Server cloud instances aligns with your go-to-cloud strategies.

Good luck!

Diego E. KESSELMAN