Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

vRanger 7.8.5 - Installation/Upgrade Guide

Navegación de contenido

Key benefits Major feature list Target audience Recommended additional reading

Before you install

Trial license Single license limitation

vRanger installation overview Installing the vRanger server

Available backup transports Installing vRanger in a virtual machine (VM)

Available transports HotAdd backups (VMs only) LAN backups Considerations for installing vRanger in a VM

Installing vRanger on a physical server

Available transports LAN-free backups (VM backups only) LAN backups Installing with other applications

Optimizing your network for backups

Installing the vRanger database

Database options Installing the databases

Sizing the catalog database

Installing the vRanger virtual appliance (VA)

VA usage Deployment locations

Creating a vRanger repository

Repository storage devices Bandwidth to repositories Repository size

Configuring vCenter permissions

System requirements and compatibility

Minimum hardware requirements

Minimum hardware requirements

vRanger: physical machine vRanger: virtual machine (VM) Requirements for physical backup and restore

Supported operating systems for installation

Additional required software

Supported SQL Server versions

Supported platforms

Supported vSphere versions

Equivalent version support policy vRanger and VM snapshots

Supported Hyper-V versions Supported platforms for physical machine backup Supported virtual appliance (VA) versions Supported disk types and file systems Supported disk types Supported file systems Feature-level requirements Standard backup, restore, and replication Physical backup and restore HotAdd File-level restore (FLR): Windows FLR: Linux

Configuration requirements

Password security setting policy Port requirements

Compatibility with other applications

Microsoft Volume Shadow Copy Service (VSS)

Installing vRanger

Installing vRanger

Entering vRanger service credentials Installing the vRanger database Entering vRanger database runtime credentials Installing the vRanger Catalog Service Completing the installation

Installing the vRanger Catalog Service later

Upgrading vRanger

Migrating content from an FTP or SFTP repository

Migrating content from an FTP or SFTP repository

Migrating content from an FTP or SFTP repository

vRanger editions

Supported upgrade paths

Backing up the vRanger database Upgrading a previous vRanger installation

Updating the VSS Tools

Upgrading the vRanger Database

Performing a database upgrade

Prerequisites Upgrading the database (32-bit SQL Server) Upgrading the database (64-bit SQL Server)

Upgrading the vRanger virtual appliance (VA)

Upgrading your VA

Maintaining your scratch disk Migrating your existing scratch disk

Upgrading a previous vReplicator installation

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	Supported¹
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)²
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

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
ReiserFS¹	Supported	Not supported	Supporteda²
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

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

•

•

File-level restore (FLR): Windows

•

•

Microsoft Volume Shadow Copy Service (VSS)

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

•

•

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.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center