vRanger 7.8.3 - Installation/Upgrade Guide

Supported disk types

Supported disk types

The following table details the support status of the listed disk types for the documented vRanger functions.

 

Table 9. Supported disk types

Disk types	Backup and restore	Catalog	File-level restore (FLR)
Windows® virtual machines (VMs)
MBR	Supported	Supported	Supported
GPT	Supported	Supported	Supported1
Dynamic	Supported	Not supported	Not supported
Windows physical machines
MBR	Supported	Supported	Supported
GPT	Supported	Supported	Supporteda
Dynamic	Not supported	Not supported	Not supported
Linux® virtual machines (VMs)2
LVM	Supported	Not supported	Supported
MBR	Supported	Not supported	Not supported
GPT	Supported	Not supported	Supported
Dynamic	Supported	Not supported	Not supported

---

1

FLR supported for 2012 or later systems only when performing FLR on 2012 or newer systems. Older systems may not show data on GPT disks.

2

FLR for Hyper-V® Linux VMs is not supported.

Supported file systems

Supported file systems

The following table details the support status of the listed file systems for the documented vRanger functions.

 

Table 10. Supported file systems

File system types	Backup and restore	Catalog	File-level restore (FLR)
Windows® virtual machines (VMs)
NTFS	Supported	Supported	Supported
FAT32	Supported	Not supported	Not supported
exFAT	Supported	Not supported	Not supported
ReiserFS1	Supported	Not supported	Supporteda2
Windows physical machines
NTFS	Supported	Supported	Supported
FAT32	Supported	Not supported	Not supported
exFAT	Supported	Not supported	Not supported
ReiserFSa	Supported	Not supported	Supportedab
Linux® virtual machines (VMs)
ext2	Supported	Not supported	Supported
ext3	Supported	Not supported	Supported
ext4	Supported	Not supported	Supported
JFS	Supported	Not supported	Supported
XFS	Supported	Not supported	Supported
ReiserFS	Supported	Not supported	Supported
LVM (one physical disk)	Supported	Not supported	Supported

---

1

FLR is not supported on ReFS on Windows Server 2019.

2

FLR supported for 2012 and 2016 systems only when performing FLR on 2012 or 2016 systems.

Feature-level requirements

Feature-level requirements

Some vRanger features and functions have requirements or limitations that do not apply to the rest of the product. Review this list to ensure that all requirements are understood. The features and functions described here are:

•	Standard backup, restore, and replication

•	Physical backup and restore

•

HotAdd

•	File-level restore (FLR): Windows

•	FLR: Linux

•	Microsoft Volume Shadow Copy Service (VSS)

Standard backup, restore, and replication

Standard backup, restore, and replication

For basic backup and replication functions, vRanger supports any Guest OS that is supported by VMware. For a complete list, see the VMware Guest Operating System Installation Guide.

For advanced functions, such as file-level restore (FLR) or additional application consistency, see the requirements in the following topics:

•	File-level restore (FLR): Windows

•	FLR: Linux

•	Microsoft Volume Shadow Copy Service (VSS)

Additional replication requirements

The following limitations and requirements apply to replication:

•	vRanger replication does not operate with servers that are behind a network address translation (NAT) firewall. To replicate through a NAT firewall properly, you must have an IP tunnel in place between two NATed subnets. Contact your ISP provider to see if this option is available to you.

•

The VM hardware cannot be changed during replication. For this reason, the VM must be at a hardware version level that is compatible with both the source and target servers. The VMware® ESXi™ version of the source and target hosts does not matter, as long as the VM hardware is supported on both ESXi versions. For more information on VM hardware versions and compatibility, see the VMware documentation at https://www.vmware.com/support/pubs/.

•	A continuous connection between source and target sites is required when replication is taking place.

•	Excessive network packet loss could result in replication failure. Replication does work with links having average packet loss of less than 2%. Replication is not designed to work in replication environments where packet loss exceeds commercially accepted limits.

•	Networks having 99% uptime and availability generally provide for good Replication performance.