9.0.2.2 was the last version that supported the traditional ISO‑mount upgrade method. Beginning with 9.0.3, Broadcom consolidated multiple products into a single VMware Live Site Recovery (LSR) appliance
- VMware Live Site Recovery
- vSAN Data Protection
- vSphere Replication
Once you reach 9.0.2.2, you can deploy the new VMware Live Recovery Appliance and begin the convergence process.
Required Step Upgrade for Converge
- Snapshot your existing LSR VMs before starting.
- Export replication configuration data thorugh ui and cli
- Save any custom SRA XML files.
- You must be on LSR 9.0.2.2 before you can converge into the new consolidated appliance.
- Enhanced replication must be enabled on the VM’s that are being replicated
- Deploy a new VMware live recovery appliance on v 9.0.5 with a new IP and FQDN
- vCenter must be on 8U3 and above and ESX should be 8 U2D and above.
- Add the vCenters to the new VMware live recovery appliances /etc/hosts file
- Perform the convergence from the new appliance
- LSR preserves most configuration items, protection groups, recovery plans, management server detail
- Redo the certificates for the new appliances
- Wizard powers off your old appliances post the converge.
Download LSR 9.0.5 from Broadcom portal
Verify compatibility matrix
Deploy the new 9.0.5 appliance by using the .OVA file downloaded from the Broadcom portal, and assign it a new FQDN and IP address during deployment.
Launch the new VMware Live Recovery Appliance Management & Click Converge Legacy Appliances
Choose the vCenter to connect
Provide the credentials
It scans the inventory and shows which appliances are eligible for convergence.
Select the appliances that needs to be convergred and click Finish.
Convergence takes about 10 mins
Once complete, we will need to reconfigure the environment
At this stage, we wont be able to use our replication services.
Configure the environment
Connect to the vCenter
Provide the site name as Site A for example
The consolidated appliance has the live site recovery, vSphere replication and vdp in it.
This now pushes the 9.0.2 hbr solution into the esx host.
tail -f /var/log/vmware/eam/eam.log
The original VM’s SRM and VR appliances are powered off and it can be deleted .
Once everything settled, the environment looked and behaved like it did before aside from the new FQDN and the consolidated UI and quick failover seems to be working well.
Verify the packages
# SAVE credentials
$creds = Get-Credential
$creds.UserName | Out-File "$env:USERPROFILE\vcenter-user.txt" -Force
$creds.Password | ConvertFrom-SecureString | Out-File "$env:USERPROFILE\vcenter-pass.txt" -Force
Write-Host "Credentials saved successfully." -ForegroundColor Green
# Verify files were written correctly
Write-Host "Username file: $(Get-Content "$env:USERPROFILE\vcenter-user.txt")"
Write-Host "Password file length: $((Get-Content "$env:USERPROFILE\vcenter-pass.txt").Length) chars"
Connect-VIServer -Server "sfo-m01-vc02.ash.local" -Credential (Get-Credential)
$targetPackages = @("vmware-hbr-agent", "vmware-hbrsrv")
Get-VMHost | ForEach-Object {
$vmhost = $_
Write-Host "`n Host: $($vmhost.Name)" -ForegroundColor Yellow
try {
$esxcli = Get-EsxCli -VMHost $vmhost -V2
$vibs = $esxcli.software.vib.list.Invoke()
$filtered = $vibs | Where-Object { $targetPackages -contains $_.Name }
if ($filtered) {
$filtered | Select-Object Name, Version, InstallDate, Status | Format-Table -AutoSize
} else {
Write-Host " No HBR VIBs found." -ForegroundColor Gray
}
} catch {
Write-Host " Could not query VIBs: $_" -ForegroundColor Red
}
}
Disconnect-VIServer -Server "sfo-m01-vc01.ash.local" -Confirm:$false
References
https://knowledge.broadcom.com/external/article?articleNumber=408127
https://knowledge.broadcom.com/external/article?articleNumber=414400
https://knowledge.broadcom.com/external/article/429918/dns-resolution-fails-and-15minute-networ.html