log shipping alone

Hello Penumarthi It sounds like you want to set up “log-shipping-style” replication of a DB2 11.5.9 database running on a RHEL 8.10 VM on-prem into Azure by using Azure Site Recovery (ASR). Below is a high-level, step-by-step of how you can do this. I’ve also included pointers on how to prepare DB2 for proper recoverability after failover.

1. Prepare your DB2 database for archive logging • Enable archive logging:
   • Run:

     db2 update db cfg for <YourDB> using LOGARCHMETH1 DISK:/var/db2/archivelogs

   • Confirm:

     db2 get db cfg for <YourDB> | grep -i “Log Archive”

   • Make sure your archive log directory has enough space and is on a separate disk if possible.
2. Create and configure your Recovery Services vault in Azure • In the Azure portal, create a Recovery Services vault in the target region/resource group. • Configure a replication policy (snapshot frequency, retention window, app-consistent snapshot schedule).
3. Deploy the ASR “configuration server” on-prem • Download the ASR Unified Setup package. • Install on a Windows (or Linux) jump-box that has line-of-sight to your DB2 VM. • Register it with the vault.
4. Install the ASR Mobility Service on your RHEL 8.10 VM • Copy the Linux agent bits to your DB2 VM. • Run the install script, supplying vault credentials and selecting the replication policy. • Verify the service is up and showing healthy in the vault.
5. Enable replication for the DB2 VM • In the Azure portal, open your Recovery Services vault > “Replicate” > select your on-prem environment (VMware/Physical) > pick the RHEL 8.10 VM. • Point to your target Azure subscription, resource group, virtual network, and storage. • Assign the replication policy you created.
6. Let the initial sync complete • The agent will transfer a baseline copy of your VM disks (including your DB2 data and logs) to Azure. • Monitor progress under “Replicated items” in the vault.
7. Perform a Test Failover • Trigger a “Test failover” to spin up the replicated VM in an isolated VNet. • On the test VM, start your DB2 instance and run:

   db2 rollforward db <YourDB> to end of logs and complete

   • Verify your application can connect and that the data is intact.
8. Planned or Unplanned Failover / Failback • For planned failover, quiesce your DB2 on-prem, then run the ASR “Planned Failover” option. • After failover, roll forward DB2 to the most recent logs as above. • To fail back, reverse the process: reprotect the original VM, sync back changes, then planned failback.

That process gives you near-continuous, crash-consistent plus periodic app-consistent “log-shipping-style” recovery for your DB2 workload via ASR.

If you need more detail around any of these steps—like the exact Linux mobility service commands, DB2 rollforward syntax, network prerequisites, or how to handle archive-log pruning—just let me know!

Reference list:

• Configure Site Recovery: https://docs.microsoft.com/sql/database-engine/log-shipping/configure-log-shipping-sql-server?view=sql-server-ver15 (for general log-shipping concepts)

• High availability and disaster recovery for SQL Server in Azure VMs: https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-high-availability-dr

• Troubleshoot replication failures in Azure Site Recovery: https://supportabilityhub.microsoft.com/solutions/apollosolutions/f555e718-4565-00e0-694b-eb07489a1dc7/apollo-a75851ec-7a21-469d-8c11-75c9e481b203

• Monitor Site Recovery with Azure Monitor Logs: https://learn.microsoft.com/azure/site-recovery/monitor-log-analytics?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider

• Linux support matrix and mobility service install steps: search “Azure Site Recovery Linux” in docs.microsoft.com.