Frequently Asked Questions 


Which clouds and operating systems do you support?

Clouds: We support every major public and private cloud, including AWS, Microsoft Azure, IBM Cloud, Oracle Cloud, Google Cloud, OpenStack, CloudStack, and several more.

Operating Systems: We support every major Windows and Linux based systems, including Windows Server 2003-2016, Debian, Red Hat Linux, Ubuntu, Oracle Linux, and several more.

Please review our technology page for more details.


When I do a partial sync, do I have to wait for all the data to be synchronized?

RackWare has a file-based sync technology that only requires the changed parts of files to be synced, thus reducing the time and resources required. We can restore individual files or groups of files from any configured point in time.


Can files be restored to the source and target?

Yes, files can be restored to either source or target host.


Do you offer full or incremental backups?

We offer the flexibility of both full and incremental backups. Incremental backups save space while full backups ensure reliability.


Does RackWare support physical servers?

RackWare does not require access to any hypervisor or storage array. The Image replication is accomplished through the Operating System. RMM requires that the disk is accessible and the corresponding permissions.

For Linux, RMM uses passwordless SSH and can configure with root access or with a sudo configuration for a non-root user.

Additionally, passwordless SSH works with Windows as well as winexe. SSH avoids having to convey a user and password, however, requiring Administrator privileges.


Does RackWare support replication across disparate hypervisors?

Yes, RackWare does support replication across disparate hypervisors. Any convergence is also supported for the hypervisors. You can replicate from combinations including VMware to Xen or KVM to VMware. With the RMM, physical to virtual is also supported for any hypervisor.


What applications does RackWare support?

RackWare offers a technology called Image Capture that transparently supports virtually all applications. RMM does not recreate the Image on the Target server, but copies the Image bits and then constructs the Image as a whole in the new Target environment on to the the new hardware. Through this process, applications, configurations, application data, users, and the exact version of the Operating System are preserved. Some applications with extremely large and high IO databases may require additional setup and configuration which Rackware’s discover process can identify for consideration. Consult Rackware for additional details.


Does RackWare modify applications in the Target environment?

As a part of defaulted processes and design, RMM does not modify application settings. To enable the Image to run on the new hardware in the Target environment, only OS and infrastructure changes are supported. After replication, many applications are able to work immediately. However, some applications require setting adjustments that can be sensitive to the network IP address or other infrastructures that may be incompatible in the Target environment. For more dense projects, these can be automated via a pre and post API calls as part of replication and sync.


Does RackWare support clusters?

Yes. For simple clusters, servers are duplicated to a Target environment and only requires modifications of IP addresses. If needed, IP addresses can be automated as needed. Often, clusters can be complex and thus require additional attention.

Additional attention may be required under the following conditions:

  • With large and high IO clusters, RMM may work simultaneously with cluster specific mechanisms, especially for DR cases.

  • When drives change ownership frequently, a mechanism has to be implemented to hold the drive in place during replication and sync operations.

  • For economic reasons, it is typical to replicate or sync from a multi-node cluster to a single node cluster. This process requires a post API script to adjust the configuration on the Target side after sync operations.


Does RackWare support network storage?

Yes, RackWare supports network storage including NFS, CIFS, Fibre Channel, and iSCSI. There are various mechanisms in the RMM to accommodate network storage and to minimize and overcome deficiencies in cloud support of similar networks. Consult us for more info.


Does RackWare have an agent?

RackWare does not deploy an agent. In 1 to 3 percent of servers that are large with high IO rates, deployment of an agent can be used for aggressive RPO settings and continuous sync.


Does RackWare require root or administrative permissions?

RackWare does not require access to any hypervisor or storage array. The Image replication is accomplished through the Operating System. RMM requires that the disk is accessible and the corresponding permissions.

For Linux, RMM uses passwordless SSH and can configure with root access or with a sudo configuration for a non-root user.

Additionally, passwordless SSH works with Windows as well as winexe. SSH avoids having to convey a user and password, however, requiring Administrator privileges.


What is required on the Target and Source side for replication and sync?

Through the Operating System, RackWare performs replication and sync to then be translated into a few requirements. Credentials to the server and network access to a determined port  is required. A small number of standard OS packages and utilities are utilized by RMM. For most cases, all the needed packages are already available on production servers. If desired, the RMM can automatically install these packages.

Additionally, origin servers need sufficient storage to perform replication and sync processes. Instead of accessing a live filesystem, RMM takes a snapshot of the Image and performs all operations. It is highly recommended that each partition has around 15% of free space, but high IO rate servers may require more.


Does RackWare support encryption? If yes, please describe.

Yes, the RMM supports encryption and all data flows are encrypted by default.

Generally, the RMM Server is deployed in the Target environment which connects to the Origin environment over a WAN connection. Though the WAN connection can be over a public interface or private connection, all information traded with the Origin server is completely protected by secure protocols.

For both Windows and Linux, SSH is used for all data transfers. Likewise, SSH protects all data exchanges with the Target server.

The RMM configures SSH to use ciphers in the suggested order:

  • aes128-ctr

  • aes192-ctr

  • aes256-ctr

  • arcfour256

  • arcfour128

  • aes128-cbc

  • 3des-cbc

  • blowfish-cbc

  • cast128-cbc

  • aes192-cbc

  • aes256-cbc

  • arcfour

The preferred order and available ciphers can be customized; contact RackWare for more information.


How are Domains handled? GPOs? What type of user needs to be set up?

Through replication and sync semantics, all Domain settings and GPOs on the Target side are preserved. When booted, applications will attempt to login through the same Domain users as on the Origin. Because of this, the Target environment requires a Domain Controller with similar settings as the Origin. While the Image bits are preserved from Origin to Target, the Target boots on different hardware. The leading practice is to reset the Domain account when first booting the Target server. RackWare does not recommend changing the SID.