FEBRUARY 20, 2024

RACKWARE MANAGEMENT MODULE

VERSION 7.4.6.25 RELEASE NOTES

RACKWARE INC
Contents
1 Overview ............................................................................................................................................... 3
2 New Features ........................................................................................................................................ 3
3 Supported OSes..................................................................................................................................... 4
4 Configuration Considerations ............................................................................................................... 5
5 Known Issues......................................................................................................................................... 5
6 Issues Fixed ........................................................................................................................................... 8
7 Upgrade Considerations ....................................................................................................................... 9
8 Workarounds for External Issues .......................................................................................................... 9

RackWare Inc • Proprietary and Confidential Page 2 of 10

1 Overview
This document describes the new features, known issues, and issues fixed in version 7.4.6.25 of the
RackWare Management Module (RMM).

2 New Features

The following features are new in 7.4.6.25 relative to 7.4.5.6

An Image Name can now be specified when autoprovisioning into Google Cloude
An instance can now be autoprovisioned into OCI with multiple NICs
An instance can now be autoprovisioned into Azure with a Disk Type and an Encryption Key Type

The following features are new in 7.4.5.6 relative to 7.4.3.22

Support for Alma Linux 8, 9 including autoprovisioning those servers to any supported cloud
Support for Rocky Linux 8, 9 including autoprovisioning those servers to any supported cloud
Support for Oracle Linux 9.x and RHEL 9.x, including autoprovisioning those servers to any
supported cloud
Support for running the RMM on an Oracle Linux 7.9 server
Support for Windows 2022, including autoprovisioning those servers into any supported cloud
Support for autoprovisioning servers into Digital Ocean cloud
Support for autoprovisioning servers into Linode cloud
Various GCP cloud agents are now automatically installed on the autoprovisioned target in GCP
Drives can now be reserved on the GUI to prevent them from being used for snapshots
Can now specify a number of file systems of a server to be synced in parallel via GUI or CLI
Configure email alerts to be sent when available storage in the zfs pool is getting low via GUI
(RMM Info – RMM Config)

The following features are new in 7.4.3.22 relative to 7.4.1.4

Support for Ubuntu 20, 22, and Debian 11 operating systems, including autoprovisioning those
servers to any supported cloud.
Support for Windows 2022 migrations using pre-provisioned target servers is available via a
patch applied on top of 7.4.3.22. The patch and the instructions for applying it are at
https://rackware.freshdesk.com/a/solutions/articles/5000881363 . That same link also describes the
steps needed for autoprovisioning Windows 2022 servers into OCI. Contact RackWare Support
([email protected]) for information about autoprovisioning Windows 2022 servers into other
clouds.
Support for Windows servers that include Resilient File Systems (ReFS). The ReFS on the source
servers will be converted to NTFS on the target servers.
Support for autoprovisioning to a Zadara environment
Support for autoprovisioning to an Oracle PCA environment
RMM Storage Monitoring - configure email alerts to be sent when available storage in the zfs
pool is getting low via CLI command “rw rmm config”
By default, the RMM will now use the new Examine method
By-jobid logs no longer sometimes truncated

The following features are new in 7.4.1.4 relative to 7.4.0.583

RackWare Inc • Proprietary and Confidential Page 3 of 10

 The RMM license will remain active for up to 8 days while the RMM server is powered off
OCI Tags can now be set on the GUI when autoprovisioning to OCI
The Provision Disks field, allowing the sizes of target disks to be specified, is now available on
the GUI under Advanced Options on the Target side
The OCI Storage Key/Vault option is now available on the GUI
Custom values can now be used for the Datacenter/Region on an Azure Cloud User

The following features are new in 7.4.0.583 relative to 7.4.0.514:

The ‘rw license generate-report’ command is now available. This may help determine for which
migrations licenses have been used. Issue ‘rw license generate-report –help’ for details

The following features are new in 7.4.0.514 relative to 7.4.0.483:

• The ‘Delete from Cloud’ option is now available when deleting multiple hosts

3 Supported OSes
Migrating and Protecting servers running the following OSes is supported:
• RHEL/CentOS 5.2 through 5.11
• OEL 5.6 through 5.11
• RHEL/CentOS/OEL 6.1 through 6.10
• RHEL/CentOS/OEL 7.0 through 7.9
• RHEL/CentOS/OEL 8.0 through 8.4
• RHEL/OEL 9.x
• SLES 11
• SLES 12 (no btrfs)
• Ubuntu 10, 12, 14, 16, 18, 20, 22
• Debian 8, 9, 10, 11
• Alma Linux 8.x, 9.x
• Rocky Linux 8.x, 9.x
• Windows 2008 R2**
• Windows 2012 R1, R2
• Windows 2016
• Windows 2019
• Windows 7
• Windows 10
• Windows 2022

** Most Cloud Service Providers have ended support for Windows 2008. We recommend that you
upgrade your source servers to a later version of Windows before migrating them into the cloud. In
most cases migrations of Windows 2008 R2 will continue to work and RackWare will continue to
support these Migrations with the understanding that there are no guarantees that this version of
Windows will work in the target Cloud, and support for such systems in target Clouds is at the
discretion of the Cloud Service Provider.

RackWare Inc • Proprietary and Confidential Page 4 of 10

4 Configuration Considerations
This section describes RMM configuration changes that should be made in certain circumstances

4.1 TNG, no-reboot Configuration

When the TNG option is used with Windows DR syncs, or when the ‘no reboot’ option is used with
Windows DR syncs, the target server is left in the winpe kernel at the end of the sync operation rather
than being booted back to Windows. When these options are used, a change may need to be made to
the RMM configuration. The change is not needed if 7.4.3.22 (or greater) is the first version that has
been loaded on your RMM, but may be needed if you upgraded to 7.4.6.25 from a version of RMM prior
to 7.4.3.22.

Open the /opt/rackware/data/options file on the RMM. Search for the text
dev_useOldExamine

If the only occurrences of that string are on lines that say

#dev_useOldExamine=1

then use a text editor (e.g. vi) to make a copy of that line below it, then remove the “#” and change the
“1” to a “0”. So
#dev_useOldExamine=1
is replaced by
#dev_useOldExamine=1
dev_useOldExamine=0

Then save the file.

Next, pause any DR Policies that are running and wait for all captures and syncs to complete. Then
issue the command “rwadm restart”.

Now the RMM will come up with the dev_useOldExamine variable set to 0.

This can be verified by running “ rw rmm show -v | grep dev_useOldExamine”

5 Known Issues
5.1 Issue: The CLI command “rw wave edit-item <wave> -seq 0--reset-sync-stats direct”
does not work though the response says that ‘direct’ is a valid option.
Workaround: Use “rw wave edit-item <wave> --seq 0 --reset-sync-stats ‘host sync’

5.2 Issue: If the Filter File Path field or the Exclude File System(s) for a sync contains a “\”,
when the Modify button is pressed, the Filter File Path or Exclude File System(s) fields
will be correct. But the next time GUI screen is viewed the “\” characters will have
disappeared from the paths. If the modify button is then pressed, the path used by the

RackWare Inc • Proprietary and Confidential Page 5 of 10

 RMM will be incorrect, since it will not have the “\” characters in it. For example,
“E:Data” will be used instead of “E:\Data”.
Workaround: Once the Filter File Path or Exclude File System(s) fields have been set
correctly and modified for the first time, if the Modify button for the sync is not used
again the issue will not occur. If the modify button for this sync does need to be used,
then add the “\” characters to the Exclude File System(s) field before pressing the Modify
button. For a filter file, select ‘Remove Current Filter Paths’ press the Modify button,
then edit the screen again and reenter/reselect the desired filter file and then press the
Modify button

5.3 Issue: Stage 2 Sync fails with “RSP_SYNC_ERROR SYNC_ERROR_TRANSFER

STATUS_ERROR Details: delete_file: unlink(Windows/Temp/RackWare-
microkernel/originals/SYSTEM.LOG2) failed: Device or resource busy” while sync is at 0
pct complete
Workaround: ssh to the target server from the RMM and then issue the following
commands:
reg unload 'HKLM\ORIGINAL_SYSTEM'
reg unload 'HKLM\OFFLINE_SYSTEM'
reg unload 'HKLM\ORIGINAL_SOFTWARE'
reg unload 'HKLM\OFFLINE_SOFTWARE'
Then retry the Stage 2 Sync

5.4 Issue: Host sync AutoProvision of Linux server fails with “ERROR: CAUTION:
RackWare Microkernel fallback boot is unavailable on the target”
Workaround:
The issue is that the source /boot volume should be at least 250 MB, and it is not. Because
of this, the target /boot is too small. Do the following to work around the issue:
1) Delete the target VM in the cloud
2) On the System tab for the Sync, change the Target Type from ‘Existing System’ to
Autoprovision using the radio buttons’
3) Click on the triangle next to “Advanced Options to bring up the Right Sizing field. In the
File System ID field enter “/boot” (without the quotes), in the Size field enter “250”, and in
the dropdown enter MB. Under the target advanced setting configure for "/boot=250MB"

4) Re start the Host Sync AutoProvision

RackWare Inc • Proprietary and Confidential Page 6 of 10

 5.5 Issue: Windows Stage 1 sync of RDS servers fail with RSP_SYNC_ERROR
SYNC_ERROR_DUPLICATE_FSIDS STATUS_ERROR
Workaround:
1) Verify that your RDS Profiles are configured as intended.
2) Contact RackWare Support to obtain a patch for this issue

5.6 Issue: GUI shows “RackWare RMM Installation Incomplete”

Workaround: Issue the following CLI commands:
chmod -R 777 /opt/rackware/data/
chmod o+w /dev/null
chmod -R 0775 /var/log/rackware
chmod -R 0775 /opt/rackware/vendor/python
rwadm gui select
choose the ‘RMM Lite’ GUI
chmod -R 0777 /opt/rackware/data/ (again)

5.7 Issue: RMM GUI in OCI inaccessible after working previously

Workaround: Please do the following while logged in to the RMM CLI as 'root' (or
after executing 'sudo su'):
1. Check if permissions on /dev/null are something other than 666
[root@rmm01 ~]# ls -lrhat /dev/null
crw-r--r-- 1 root root 1, 3 Jul 21 10:21 /dev/null -> This is 644

2. If they are not 666, then change it to 666

[root@rmm01 ~]# chmod 0666 /dev/null

3. Check if it is set correctly to 666

[root@rmm01 ~]# ls -lrhat /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 21 10:21 /dev/null -> This is 666

4. In a new browser window, enter the IP address of the RMM and retry logging in
to the RMM with the correct username and password. It should now be successful

5.8 Issue: Specifying a filter file to be on the RMM fails via the GUI with “Could not parse
<file name>”
Workaround: If selecting the radio button “File Path on RMM”, place the filter file in the
/opt/rackware/ folder. Alternatively, select the radio button ‘Upload local file’ and browse
to it on your laptop.

5.9 Issue: Autoprovisioning of RHEL5 and SLES11 into GCP fails

Workaround: Due to limitations in the GCP environment, it will not be possible to
autoprovision RHEL5 servers and SLES 11 servers into GCP. Please contact RackWare
support (support @rackwareinc.com) for details.

RackWare Inc • Proprietary and Confidential Page 7 of 10

 5.10 Issue: Autoprovisioning into vCenter fails with “Could not find iso
/opt/iso/systemrescuecd-x86-5.2.2.iso”
Workaround: Please contact [email protected] for instructions on where to
download the needed file.

6 Issues Fixed

6.1 This section describes issues fixed between version 7.4.5.6 and 7.4.6.25
• Sync2 no longer fails with ‘no space left on device’ when compression attribute on source
file changes (
• Ubuntu 22 migrations to GCP now choose an Ubuntu 22 image initially
• Sync1 no longer fails with ‘Open <file> no space left on device’ when server has around 8
million files in a directory
• Windows 2008R2 and 2012 can now be autoprovisioned into GCP
• Autoprovision of Windows 2008R2 into Azure successful though 2008R2 images no longer in
Azure
• RMM will always use the private IP address to connect to a GCP target if the private IP
connection is working

6.2 This section describes issues fixed between version 7.4.3.22 and 7.4.5.6
• RMM installation on OL 7.9 now supported
• Sync no longer fails with ‘Insufficient Target Space’ when source and target BIOS boot
partitions have the same GPT UUID and –delete-all-target-fs option used
• Migrated server with an xfs file system now has correct ftype
• PV Xen instance running a UEK kernel with OL 5.6 now migrated correctly
• Syncs of ubuntu 18 servers with multipath enabled and no LVM volumes now
• Linux targets with root fs and /usr on lvm volumes no longer stuck in emergency shell
• AWS govt cloud clouduser now added successfully
• GCP AP when GCP has OS Login enabled now successful
• Windows targets now formatted correctly when source has NTFS fs with cluster size greater
than 64 KiB
• Windows BIOS-UEFI now succeed when boot volume mounted at a subdirectory
• Windows targets now boot when source bootmgr is compressed
• OpenStack/cloud-init “config drive” now automatically excluded from syncs by default
• Syncs now successful when FAT fs is on a whole disk device
• Host syncs no longer fail with “forwarding failed” after previous tunnel was closed on one
side
• Windows delta syncs now successful when ssh key on source atypically formatted
• Sync now successful when source has invalid swap entry in fstab
• VCN Compartment field on GUI now displays correct value
• Error message now correctly identifies when a linux snapshot has been invalidated
• Full filenames now visible on GUI File Restore page
• Azure NICs now provisioned in the VM’s resource group

RackWare Inc • Proprietary and Confidential Page 8 of 10

 • Linux servers with kernel module files that are symlinks now migrate successfully
• Improved error message if source server has unsupported architecture
• File system checks now run on image file systems before mounting them
• Target hostname field now always visible on GUI when autoprovisioning
• Syncs of older windows machines with an ESP on a BIOS machine are now successful without
manually excluding the file system

6.3 This section describes issues fixed between version 7.4.1.4 and 7.4.3.22
• Windows 2019 hosts migrated to GCP now are classified as Windows 2019 hosts on GCP
console
• GCP clouduser added successfully when there are no networks present in active regions
• ec2-api-tools (including log4 jar file) no longer present on the RMM
• RHEL7.5 server now booted into Rackware microkernel during AP to Azure

6.4 This section describes issues fixed between version 7.4.0.583 and 7.4.1.4
• Azure Government Cloud Datacenters now available in dropdown when adding Cloud User
• GUI now allows the source and target friendlynames to be the same as the hostname

7 Upgrade Considerations

7.1 Targets in Winpe

Before upgrading to the current from any previous version of RMM, if there are any
target servers booted into winpe (note that if a sync is using the TNG option, then the target server will
be booted into winpe), please boot them into Windows before upgrading the RMM. This can be done
by issuing the CLI command ‘rw host release <friendlyname of target host>’. This will cause the target
host to be booted from winpe to Windows. Once this has been done for all target hosts, the RMM may
be upgraded.

8 Workarounds for External Issues

Sometimes a 3rd party makes a change to their software/environment such that special steps are
needed by the RMM user to migrate or protect servers. This section describes those workarounds.

8.1 Issue: Autoprovisioning of Windows 2008 servers into OCI fails.

Workaround:
Since OCI no longer provides Windows 2008 Platform Images, a special procedure must be used
for autoprovisioning Windows 2008 servers. The manual Migrating Windows 2008R2 Servers to
OCI Using Flex Shapes contains the instructions to follow.

RackWare Inc • Proprietary and Confidential Page 9 of 10

 8.2 Issue: Autoprovisioning of RHEL5.x servers into OCI fails
Workaround:
Since OCI no longer provides RHEL5 Images, a special procedure must be used for
autoprovisioning RHEL5 servers. The manual Migrating RHEL5 Servers to OCI contains the
instructions to follow.

RackWare Inc • Proprietary and Confidential Page 10 of 10