• ポータルについて詳しく知る
• ダウンロード
• 印刷
• MY ダウンロード ()

• サポート
• 技術文書
• vRanger 7.8.2
• vRanger 7.8.2 - Installation/Upgrade Guide

vRanger 7.8.2 - Installation/Upgrade Guide

コンテンツのナビゲーション  

Introduction

Key benefits Major feature list Target audience Recommended additional reading

Before you install

Trial license

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

• Viewing Topics 57 - 60 of 92

×

Physical backup and restore

System requirements and compatibility > Supported platforms > Physical backup and restore

---

Physical backup and restore

•	Ensure that the physical server is running a supported operating system. Refer to Supported platforms for physical machine backup for more information.

•	Ensure that the physical server is not booting into UEFI. The vRanger Boot CD does not support UEFI.

HotAdd

System requirements and compatibility > Supported platforms > HotAdd

---

HotAdd

To perform backup/restore/replication tasks using HotAdd, vRanger must be installed on a VM. Also:

•	HotAdd only works on SCSI and SATA disks. IDE disks and vRDMs are not supported.

•	Datastores for the target VMs must be accessible to the vRanger VM.

•	vRanger can only perform operations on VMs within the same data center.

•

HotAdd cannot be used if the VMFS block size of the datastore containing the VM folder for the target VM does not match the VMFS block size of the datastore containing the vRanger VM. For example, if you back up a virtual disk on a datastore with 1 MB blocks, the proxy must also be on a datastore with 1 MB blocks.

•	Backing up thick disk requires the maximum disk size to be available. When backing up a thick disk, the vRanger VM’s datastore must have at least as much space available as the maximum configured disk size for the VM to be backed up.

•	When using vRanger with machine based HotAdd to backup encrypted VMs, the vRanger VM must also be encrypted.

•	When using vRanger with VA-based HotAdd to backup and replicate encrypted VMs, the VA must also be encrypted.

File-level restore (FLR): Windows

System requirements and compatibility > Supported platforms > File-level restore (FLR): Windows

---

File-level restore (FLR): Windows

To perform FLR from a Windows® VM, the VM must be a supported disk type. For more information, see Supported disk types.

FLR: Linux

System requirements and compatibility > Supported platforms > FLR: Linux

---

FLR: Linux

Review the following information to understand the functions and limitations of the vRanger Linux® FLR feature.

•	Linux FLR requires the vRanger VA.

•	vRanger requires you to recover the Linux files to an intermediate Windows® machine. When you recover Linux files to a Windows machine, you lose the file permissions.

•	The source VM properties need to show the operating system (OS) type as Linux. If this feature is not configured properly, vRanger cannot identify the savepoint as a Linux VM.

•	For a list of supported file systems, see Supported disk types and file systems.

•  前回
• Viewing Topics 57 - 60 of 92
• 次へ 

この文書を検索 この製品バージョンに対応するすべての文書を検索 この製品に対応するすべての文書を検索 すべての文書を検索

×

 サポートへようこそ

Quest *product*のオンラインサポートヘルプは、関連会社のサポートサイトで参照できます。「Continue（続行）」をクリックすると、*product*の適切なサポートコンテンツとアシスタンスへ移動します。

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center