Anda di halaman 1dari 116
Note: The term Data Protection Platform is abbreviated as DPP in the product and in

Note: The term Data Protection Platform is abbreviated as DPP in the product and in this course.

This 4.1 course has been appended to the 4.0 course and is limited to what is new about vRanger Pro 4.1 DPP. So all of the basic 4.x tasks that have not changed and are already covered in the 4.0 course will not be repeated here.

Note: If you need a refresher on how to schedule backups and other 4.x–related tasks, please review the vRangerPro40 Backups module in the vRanger Pro 4.0 DPP course found in the Vizioncore Training Center at http://training.vizioncore.com.

Details about the last three agenda items are discussed in the following slides. 2

Details about the last three agenda items are discussed in the following slides.

Attend the Training Course Steps: 1. Go to the Vizioncore Training Center at http://training.vizioncore.com 2.

Attend the Training Course Steps:

1. Go to the Vizioncore Training Center at http://training.vizioncore.com

2. Selfregister with a business email address

3. Identify yourself as a Vizioncore customer, partner, or employee

4. Enroll in one or more training courses

5. Download course resources (e.g., course PDF file(s) as your textbook)

Download the Textbook that accompanies the Lectures In step 5 above, we encourage you t o download th e PDF file th a t accompan i es th e PPT slide d eck . It includes instructor notes and serves as the textbook for the course. Please refer to the PDF file page that corresponds to the instructor’s referenced PPT slide during the lectures.

In this slide, you can see that the PDF file and other course resources appear after the lectures at the bottom of the page. Click on the file resource’s link to save the file locally or click on a video link to launch a video.

We Append dot Releases to the MajorRelease Course Much of the 4 .1 product is exactly the same as the 4 .0 product (e.g., hardware or software requirements) . Rather than create a separate course for vRanger Pro 4.1 DPP that contains information already found in the 4.0 course, we have instead created new 4.1 specific training modules and have appended them to the existing vRanger Pro 4.0 DPP course. Anything common to both the 4.0 product and the 4.1 product already exists in the 4.0 course and is purposely omitted from the 4.1 course.

So when you want to see what’s new and different in 4.1, you would download the 4.1 PDF file (not shown), launch the appropriate 4.1 module, and listen to the lecture while following along with the PDF file.

But to learn about something in 4.1 that hasn’t changed since the 4.0 product, then we refer you to the 4.0 course. For that course, you will download the vRanger Pro 4.0 DPP training course PDF file.

• vRanger Pro 4.1 DPP New Features The course will initially provide a New Features

vRanger Pro 4.1 DPP New Features

The course will initially provide a New Features summary and then provide details later in the course .

Upgrading from earlier vRanger Pro Versions

The course will cover upgrading from vRanger Pro 3.x and 4.0 DPP.

Best Practices Configuring vRanger Pro 4.1 DPP

vRanger Pro 4.x DPP can transfer an incredible amount of data to the repositories. The product’s speed is one of the reasons that it was awarded a Best of VMworld 2009 Gold Award. But some customers‘ environments were overwhelmed b y a ll of t h e d ata an d were receiving CIFS errors. The course will discuss global settings best practices to throttle down the transfers to minimize or eliminate those kinds of errors.

Note: One v4.1 improvement is that the Regional OS Settings need not be US English, which is intended for our international customers. This topic is not mentioned elsewhere in this course.

• Module 1 – 4.1 New Features Overview M od u le 1 i ntro

Module 1 – 4.1 New Features Overview

M od u le 1 introd uces Th e new vRanger Pro 4 .1 DPP features an d t h en discusses t h ese features in greater detail later in the course.

Module 2 – New Installation and Upgrades

Module 2 discusses when to do a new installation and an upgrade.

Module 3 – Configuration Best Practices

Modules describes some troubleshooting and best practice steps to maximize the speed of vRanger Pro 4.1

DPP so that you can do backups in a smaller backup window.

Module 4 – Import Legacy Backup Jobs

Module 4 discusses how to import vRanger Pro 3.x scheduled jobs into vRanger Pro 4.1 DPP.

Module 5 – Restores

Module 5 discusses the different ways to do restores.

6
7
8
Before we can discuss what’s new in vRanger Pro 4.1 DPP, it is important that

Before we can discuss what’s new in vRanger Pro 4.1 DPP, it is important that we understand vRanger Pro 3.x an d 4 .x man ifests since some of t h e new 4 .1 features relate to t h ose man ifests an d we may want to restore vRanger pro 3.x backups into 4.1.

In general, the manifests are XML files that are created during a backup to track information about the backup job. Additionally, in 4.x, there is a global manifest file for each added repository.

This slide shows the two files that make up a vRanger Pro 3.x backup. 3.x

This slide shows the two files that make up a vRanger Pro 3.x backup. 3.x jobs could be a full backup or different ial b ack up. Incrementa l b ack ups were not supporte d .

In this example, the VM was a 20GB Windows 2003 server. The compressed backup file has a .TVZC file extension (where TVZC = “tarvizioncorecompressed”).

The manifest file has an extension of .INFO. A sample of its XML contents appears in the slide.

Other vRanger Pro 3.x facts

Besides .TVZC, other vRanger Pro 3.x backup file extensions include:

*.VZC = VCB Backups for ESX and ESXi *.VMDK = Uncompressed backups (nozip option). This option is used with repositories that do data deduplication (e.g., EMC® Data Domain) and require unzipped archives.

During backup, by ignoring white space (blanks) and compressing the rest of the VM, the 20GB VM was

reduced in size to 4,262,485 KB (4.065 GB which fits on a single layer DVD, can be mailed to a secondary site, and by running another copy of vRanger Pro at the secondary site, can restore the 20GB VM).

Importing Legacy 3.x Jobs into vRanger Pro 4.1 DPP After scheduling a vRanger Pro 3.x job, the job’s corresponding CLI (command line interface) commands are placed in the Windows Task Scheduler. This is important to know because when vRanger Pro 4.1 DPP imports 3.x jobs, it will look in the Windows Task Scheduler for those 3.x jobs. The importing of 3.x jobs is discussed in more detail in module 4.

vRanger Pro 4.1 DPP has two types of manifests ‐ Global Manifests and Savepoint Manifests.

vRanger Pro 4.1 DPP has two types of manifestsGlobal Manifests and Savepoint Manifests.

Global Manifest Whenever you add a repository, that repository contains a global manifest XML file that provides details about the repository. As you do backups, each savepoint becomes a separate folder in the repository and a corresponding entry is placed in the global manifest file. The global manifest file is required when restoring a deleted repository.

Savepoint Manifests Whenever you do a backup, the job writes a savepoint to the specified repository along with a corresponding savepoint manifest XML file. The savepoint manifest provides details about the backup job. The savepoint manifest is placed in the repository’s folder for that job. The savepoint manifest is required when restoring a savepoint.

Savepoint Manifest Example So if you define an incremental job with, say, a Threshold Count =2 as your Space Saving Technology, you will get a full backup savepoint and two incremental savepoints. Note: the first savepoint of an incremental job is always a full backup.

Each of the three savepoints will have their own savepoint manifest. These savepoints and their respective manifests will be placed in a single folder in the repository that represents the job.

• Global Manifest Af ter a repos i tory is a dd ed to vR

Global Manifest

After a repository is a dd ed to vRanger Pro 4 .1 DPP, a Glob a lManifest.metad ata XML fil e is created in t h at repository. If you have multiple repositories, each repository will have its own unique GlobalManifest.metadata file.

Referring to the circled, numbered items in the screenshot:

1. In the screenshot, click Add to add a CIFS repository.

2. Specify the CIFS properties and click Save. The added repository appears under My Repositories in the left pane.

3. Viewing the repository folder, we see the GlobalManifest.metadata file that has been created.

4. Opening the GlobalManifest.metadata file with an editor like WordPad or Notepad++ displays the XML.

Warning: Do not edit the GlobalManifest.metadata file unless asked to do so by Vizioncore Support.

• Savepoint Manifests (1) In the above screenshot, we clicked on the My Jobs button

Savepoint Manifests (1)

In the above screenshot, we clicked on the My Jobs button (outlined in red), and scheduled an incremental job to backup a single VM.

The Job Template Detail shows (circled in red) the following:

The job name MBIncremental3

The single VM Inventory Node that we are backing up MBTest VM

The Space Saving Technology job type = Incremental Backups.

• Savepoint Manifests (2) Cli ck t h e M y R epos i tor

Savepoint Manifests (2)

Cli ck t h e M y R epos itories b utton (out li ned in red) an d t h en cli ck t h e target repository to disp lay t h e repository’s savepoints. We can see that after our scheduled job ran, the new savepoint appeared in the target repository.

Note: Even though the we requested an incremental backup, the first backup of the set is always a full backup and the subsequent backups are incrementals. A set consists of a “parent” full backup and one or more “child” incrementals. The set is used when doing full restores.

• Savepoint Manifests (3) In t h e screens h ot, re f err i

Savepoint Manifests (3)

In t h e screensh ot, referring to t h e circled num b ers:

1. We see that there is a new folder that has appeared in our repository directory structure and represents

the full backup that we just performed.

2. Drilling down through the directory structure, we see two, small, XML metadata files and the archive

itself stored as a 2,209,304KB .var file. The Manifest.metadata file is the savepoint manifest. The savepoint manifest and the Vmconfig.metadata file together are equivalent to the vRanger Pro 3.x .Info file.

3. Opening up the .Manifest.metadata file, we see a partial screenshot of the XML contained within.

Savepoint Manifests and restoring from tape (CIFS only) In the future, we may decide to “sweep” this savepoint to tape by writing these three files to tape. We may then decide to remove the savepoint entirely from vRanger Pro 4.1 DPP. If removed, the savepoint entry will disappear from the global manifest file and the savepoint folder structure and files will be removed from the repository. Details on how to restore these three files from tape are described in detail in module 5. When we restore savepoints from tape, we require the savepoint manifest file.

Note: This feature only works for CIFS repositories.

16
• Backup Functions Scheduled Backup Job Im p ortation: vRanger Pro 4.1 DPP can import

Backup Functions

Scheduled Backup Job Im p ortation:

vRanger Pro 4.1 DPP can import legacy vRanger Pro 3.x scheduled backup jobs from the Windows Task Scheduler, allowing you to run only one version of vRanger Pro.

Restore Functions

Note: all Windows savepoint backups retain NTFS access control lists (ACLs). These ACLs are reapplied during all restore types.

Restore from Savepoint:

This is the standard method of doing a VM restore using a global manifest and has not changed since vRanger Pro 4.0.

Res tore f rom Savepoi n t Manif es t:

This is the method of doing a VM restore when the savepoint is not in a repository only using the savepoint manifest. No global manifest is used.

Restore from Legacy Backup:

vRanger Pro 4.1 DPP can restore legacy vRanger Pro 3.x backup files, allowing you to run only one version of vRanger Pro.

File Level Restore:

vRanger DPP Version 4.1 can perform a file level restore, restoring files and folders from a savepoint that is used to restore the entire VM image.

Fil e Leve l Res tore f rom Manif es t:

vRanger DPP Version 4.1 can perform a file level restore when the savepoint is not in a repository only using the savepoint manifest. No global manifest is used.

Restore a Repository:

vRanger Pro 4.1 DPP Version 4.1 can now perform restores from a Read Only Repository, especially useful when the repository is replicated to a secondary disaster recovery site and you need to do restores there. Previous versions of vRanger Pro DPP could only restore from repositories that had read/write access.

Operational Functions

vRang er Pro 4.1 DPP can now be patched without a full uninstall/install procedure. vRang er Pro 4.1 DPP now supports the VMware Intel E1000 virtual nics.

Q1. What is the purpose of a vRanger Pro manifest? A nswer: Th e vR

Q1. What is the purpose of a vRanger Pro manifest?

Answer: Th e vRanger Pro man ifest contents inc lu d e:

The backup contents

Parameters (compression, etc.)

Repository Location

VMX file details

Job errors

Q2. What file format do vRanger Pro manifests use? Answer: XML

Q3. What manifest is automatically created when you add a repository to vRanger Pro 4.1 DPP? Answer: Global manifest

Q4. What manifest is automatically created when you do a vRanger Pro 4.1 DPP backup? Answer: Savepoint manifest

• Lesson 1 – Manifests M an if ests are XML fil es t h

Lesson 1 – Manifests

M an ifests are XML fil es t h at store t h e d eta il s of a b ack up j ob . vRanger Pro 3.x uses an .Info file as its manifest. vRanger Pro 4.1 has a global manifest for each repository and a savepoint manifest for each backup. The 4.1 global manifest maintains a list of all of the savepoints for the repository.

Lesson 2 – New Features Overview

Backup Job Functions

– Scheduled 3.x Backup Job Importation from the Windows Task Scheduler.

Restore Functions

– Read Only Repository – can restore files from tape without having to first edit the existing repository.

– Non repository Backup Files – restore files no longer in the repository (e.g., because backed up to tape).

– Backup File Restoration – restore vRanger Pro 3.x and 4.0 images and files.

– Restore from Savepoint Manifest – the global manifest and repository directory structure are not needed.

– File Level Restore from Savepoint Manifest – the global manifest and repository directory structure not needed.

Operational Functions

– Can now patch the vRanger Pro 4.1 DPP without having to uninstall and then reinstall the product.

– vRanger Pro 4.1 DPP now supports the VMware VMnet 1000 nics.

Module 2 discusses a new vRanger Pro 4.1 DPP installation and also how to upgrade

Module 2 discusses a new vRanger Pro 4.1 DPP installation and also how to upgrade to vRanger Pro 4.1 DPP from earli er versions of vRanger Pro.

• Lesson 1 – Installation L esson 1 d escr ib es a new i

Lesson 1 – Installation

L esson 1 d escrib es a new install of vRanger Pro 4 .1 DPP.

Lesson 2 – Upgrading from vRanger Pro 3.x

Lesson 2 describes upgrading from vRanger Pro 3.x to vRanger Pro 4.1 DPP. vRanger Pro 4.1 DPP is installed

into a new folder or server and the 3.x scheduled jobs are imported into 4.1

Lesson 3 – Upgrading from vRanger Pro 4.0

Lesson 3 describes the patch that you apply to vRanger Pro 4.0 DPP to upgrade it in place to 4.1.

22
This slide refers to doing a new installation of vRanger Pro 4.1 DPP where you

This slide refers to doing a new installation of vRanger Pro 4.1 DPP where you are either:

D oing a new install of vRanger Pro 4 .1 DPP an d d o not h ave a previous version of vRanger Pro install ed .

Upgrading from vRanger Pro 3.x. The 3.x to 4.1 upgrade is covered in lesson 2.

Do not use this installation file if you are upgrading from vRanger Pro 4.0 DPP. If you already have 4.0 installed, then you must download a separate patch file that performs the upgrade from 4.0 to 4.1. The 4.0 to 4.1 upgrade process is covered in lesson 3.

Go to http://downloads.vizioncore.com/ and click the vRanger Pro 4.1 DPP icon to place the entry in the download queue. Lesson 3 of this module, Upgrading from vRanger Pro 4.0, has screenshots on how to complete a similar download.

Note: See the vRanger Pro 4.0 DPP course for these installation related topics:

Hardware Requirements

Software Requirements

Supported Guest Operating Systems

Supported Platforms

vRanger Pro 4.1 DPP New Installation Steps The steps to install vRanger pro 4.1 DPP

vRanger Pro 4.1 DPP New Installation Steps

The steps to install vRanger pro 4.1 DPP are essentially the same as 4.0, but there are a couple of cosmetic changes so we have included an updated list of steps in the slide.

The cosmetic changes are:

Step 4 has increased the minimum disk space required to 274MB, up from 227MB.

Step 6 has been added for administrators who do not have .NET Framework 3.5 SP1 already installed.

vRanger Pro 4.1 DPP Uninstall Steps The steps to uninstall vRanger pro 4.1 DPP are

vRanger Pro 4.1 DPP Uninstall Steps

The steps to uninstall vRanger pro 4.1 DPP are essentially the same as 4.0, but there are a couple of cosmetic changes so we have included an updated list of steps in the slide.

The cosmetic changes are:

Step 1c now has you select vRanger Pro rather than vRanger Pro 4.x.x.

Step 3b, uninstalling .NET 3.5 SP1, now automatically removes earlier .NET versions. The 4.0 instructions had you manually remove the earlier .NET versions.

26
This is not really an upgrade. You are installing a new copy of vRanger Pro

This is not really an upgrade. You are installing a new copy of vRanger Pro 4.1 DPP in a new folder or server an d t h en simp ly import ing t h e 3 .x j ob s as XML fil es from t h e vRanger Pro 3 .x server. Th at is a ll you h ave to d o.

Since vRanger Pro 4.1 DFPP can restore 3.x backups, we only need vRanger Pro 3.x so that we can do the one time import of the 3.x scheduled jobs and bring those jobs into 4.1. Details on importing vRanger pro 3.x backup jobs are covered in Module 4.

All vRanger Pro 3.x customers with a valid support and maintenance contract should have automatically received their 4.x licenses via email. Those customers should email sales@vizioncore.com if they did not receive their 4.x license. The 4.x licenses work for both vRanger Pro 4.0 DPP and 4.1 DPP.

As a best practice, consider running both vRanger Pro 3.x and 4.1 in parallel to backup your most critical servers until you are confident that vRanger Pro 3.x can be removed and that vRanger pro 4.1 DPP can backup your servers and can successfully restore the 3.x legacy backups and its own 4.1 backups.

These capabilities will be added to vRanger Pro 4.x DPP, but for now, if you want to do these following tasks, you must continue to use vRanger Pro 3.3:

Use the VCB (VMware Consolidated Backup) framework

Backup ESXi

Do P2VDR (physicaltovirtualdisaster recovery, e.g., backup a physical server to a VM)

28
Upgrading from vRanger Pro 4.0 Upgrading from vRanger Pro 4.0 DPP to 4.1 just requires

Upgrading from vRanger Pro 4.0

Upgrading from vRanger Pro 4.0 DPP to 4.1 just requires running a patch. There is no need to uninstall the old version and then install the new version.

Before you begin the upgrade, steps 1 and 6 advise you to backup your vRanger Pro 4.0 DPP database.

Note: Towards the end of the patch upgrade, you are warned that you will have to restart the vRanger Pro Service after the upgrade completes. When the upgrade completes, if vRanger Pro 4.1 starts up successfully, there is no need to restart the vRanger Pro Service.

If vRanger Pro 4.1 starts up but cannot connect to the vRanger Pro Service, close vRanger Pro 4.1 DPP and wait 1 2 minutes to allow the vRanger Pro Service to complete loading into server memory. Launch vRanger Pro 4.1 DPP again. It should connect successfully to the vRanger Pro Service. If the application still cannot connect to the service, restart the service by clicking Start > Run > services.msc > click the vRanger Pro Service > Restart > wait 2 minutes > relaunch the a pp lication. That should do it.

Your vRanger Pro 4.x license that used for 4.0 is also automatically used for 4.1. No licensing changes have to be made during or after the upgrade.

Upgrading from vRanger Pro 4.0 (details) Step 1: The steps on how to backup the

Upgrading from vRanger Pro 4.0 (details)

Step 1: The steps on how to backup the vRanger Pro 4.0 database, are discussed in the Vizioncore Knowledgebase article titled Manual vRanger DPP Database backup and Restore found on http://www.vizioncore.com/support/knowledgebase/index.php.

Step 2: Download the upgrade patch from Vizioncore’s Download page from your vRanger Pro 4.0 DPP server.

Refer to the circled, numbered icons in the screenshot:

1. Go to http://www.vizioncore.com and click the Download tab.

2. Click the blue icon for the Software Update for vRanger Pro 4.1 DPP to add it to the download queue.

3. Click the Download Now! Button.

4. Type in your email address and click Continue.

5. In your received email, click the download link.

6. At the File Download prompt, click Save and save the file to any folder (e.g., c:\download).

Upgrading from vRanger Pro 4.0 (details continued) Steps 3 ‐ 6: Refer to the circled,

Upgrading from vRanger Pro 4.0 (details continued)

Steps 3 6:

Refer to the circled, numbered icons in the screenshot:

1. Double click vRangerProUpgrade4.1.1.12614 (see the note below)

Note: You should only install the most recent version of the patch. The most recent version, at the time of writing this course, is 4.1.1.12614, released on October 29, 2009. So use this version or newer. The 4.1.1.12614 Release Notes can be found at http://www.vizioncore.com/products/vRangerPro/documents/release notes.php

2. Click Run.

3. At the Upgrade to 4.1.1.12614 prompt, click Yes .

4. At the “backup your database first recommendation, click Yes (if you have already backed up your database in step 1)

Upgrading from vRanger Pro 4.0 Step 7: At the Welcome to the vRanger Pro Upgrade

Upgrading from vRanger Pro 4.0

Step 7: At the Welcome to the vRanger Pro Upgrade Setup Wizard page, click Next .

Upgrading from vRanger Pro 4.0 Step 8: At the License Agreement page, click I Agree

Upgrading from vRanger Pro 4.0

Step 8: At the License Agreement page, click I Agree .

Upgrading from vRanger Pro 4.0 Step 9: At the Welcome to the Vizioncore vRanger Pro

Upgrading from vRanger Pro 4.0

Step 9: At the Welcome to the Vizioncore vRanger Pro Database Setup Wizard page, click Next .

Upgrading from vRanger Pro 4.0 Step 10: At the Upgrade Database page, select the Install/Upgrade

Upgrading from vRanger Pro 4.0

Step 10: At the Upgrade Database page, select the Install/Upgrade on an existing SQL Server 2005/2008 radio button. Then select either SQL Server or Windows Server Authentication as is appropriate to your environment and click Next .

Note: If you prefer to use SQL Server Authentication, especially if Active Directory is not available, the default SQL Server ID=vrangerprouser and the default password=V!ZionC0re (the password is case sensitive).

Upgrading from vRanger Pro 4.0 Step 11: At the Installation Database Credentials page, Refer to

Upgrading from vRanger Pro 4.0

Step 11: At the Installation Database Credentials page,

Refer to the circled, numbered icons in the screenshot:

1. Click Verify to test the connection.

2. Click OK at the Connection Successful popup.

3. Click Next (grayed out in the screenshot but will be active after clicking OK in the prior step). Click Next again.

Upgrading from vRanger Pro 4.0 Step 12: At the Existing vRangerPro Database Found page, click

Upgrading from vRanger Pro 4.0

Step 12: At the Existing vRangerPro Database Found page, click Yes .

Note: The warning that you need to restart the vRanger Pro Service after the upgrade is rarely needed. However, after a successful upgrade, the vRanger Pro Service should automatically restart without your intervention.

After the upgrade, the vRanger Pro 4.1 DPP application will start and if the application cannot connect to the vRanger Pro Service, then wait 1 2 minutes and try again.

If the application still cannot connect to the service, manually restart the service by , restart the service by clicking Start > Run > services.msc > click the vRanger Pro Service > Restart > wait 2 minutes > relaunch the application. The application should then successfully connect to the vRanger pro Service.

Upgrading from vRanger Pro 4.0 Step 13: At the Vizioncore Database Setup page, Refer to

Upgrading from vRanger Pro 4.0

Step 13: At the Vizioncore Database Setup page,

Refer to the circled, numbered icons in the screenshot:

1. Click Automatic Setup.

2. When the database has completed upgrading, click Next .

Upgrading from vRanger Pro 4.0 Step 13 (continued): At the “Database installed successfully…” Message page,

Upgrading from vRanger Pro 4.0

Step 13 (continued): At the “Database installed successfully…” Message page, click Finish.

Upgrading from vRanger Pro 4.0 Step 13 (continued): At the Completing the vRanger Pro Upgrade

Upgrading from vRanger Pro 4.0

Step 13 (continued): At the Completing the vRanger Pro Upgrade Setup Wizard page, click Finish. vRanger Pro

4.1

Pro DPP should launch successfully. All of your 4.0 configuration settings and jobs should be present in the

4.1

server.

Q1. True/False. When upgrading from vRanger Pro 3.x or 4.0, you must purchase new licenses.

Q1. True/False. When upgrading from vRanger Pro 3.x or 4.0, you must purchase new licenses. Answer: Fa lse. vRanger Pro 3 .x users must get new li censes, b ut t h ey are free. Registered 3 .x users sh ou ld have already received their 4.1 licenses via email. The licenses used by vRanger Pro 4.0 DPP users already work with 4.1. So unless the 4.0 users have evaluation licenses that will expire within 30 days, no action is necessary.

Q2. True/False. If you are upgrading from vRanger Pro 3.x to 4.1, you should install 4.1 into the same directory where 3.x already resides. Answer: False. vRanger Pro 4.1 DPP must be installed into a different folder or server than where vRanger Pro 3.x resides. Installing vRanger Pro 4.1 DPP in the same directory where vRanger Pro 3.x resides removes all of the 3.x scheduled jobs. Instead, install vRanger Pro 4.1 DPP into a new folder or server and import the 3.x jobs into 4.1.

Q3. To upgrade from vRanger Pro 4.0 DPP to 4.1, you must install a patch on the 4.0 server that you download from the Vizioncore web site downloads page. Answer: True. You must download the Software Update for vRanger Pro DPP patch from the Vizioncore Downloads page at http://downloads.vizioncore.com

Q4. What version of the .NET Framework is automatically installed with vRanger Pro 4.1 DPP? Answer: .NET 3.5 SP1.

• Lesson 1 – New Installation L esson 1 covere d t h e i

Lesson 1 – New Installation

L esson 1 covered t h e install at ion an d un installat ion of vRanger Pro 4 .1 DPP. You are on ly d oing t his installation if you never had any versions of vRanger Pro before or if you are upgrading from vRanger Pro 3.x. A overview of the upgrade from 3.x to 4.1 was then discussed in lesson 2.

Lesson 2 – Upgrading from vRanger Pro 3.x

Lesson 2 was a one slide overview about upgrading from vRanger Pro 3.x to vRanger Pro 4.1 DPP. With a new copy of vRanger Pro 4.1 DPP installed (see lesson 1), lesson 2 described the need to import the 3.x scheduled jobs and that vRanger Pro 4.1 DPP can restore backups created in 3.x if you have the 3.x backup’s .INFO file. Module 4 covers the details of the 3.x scheduled job import process.

Lesson 3 – Upgrading from vRanger Pro 4.0

Lesson 3 provided the specific steps on how to upgrade from vRanger Pro 4.0 DPP to 4.1.

Let’s now discuss Configuration Best Practices. 43

Let’s now discuss Configuration Best Practices.

• Lesson 1 –Configuration Best Practices 44

Lesson 1 –Configuration Best Practices

45
• Configuration Best Practices (1) O n Sept em ber 3, 2009 , Vi z

Configuration Best Practices (1)

O n Sept em ber 3, 2009, Vi z ioncore announce d tha t vRanger P ro DPP won the t op “Bes t o f VM wor ld 2009 ” G o ld

Award for Business Continuity and Data Protection: http://www.vizioncore.com/company/pr/press/2009/090309Best OfVMAward.pdf.

One of the reasons vRanger Pro DPP won this award was because of its speed. Its Direct to Target architecture allows an almost unlimited number of ESX servers to directly connect to one or more disk repositories.

Direct to Target Backups and restores go direct to tar g et”, using a direct communication p ath between the ESX hosts and repositories. The vRanger service does the scheduling but no backup/restore data actually passes through the vRanger Pro server. vRanger Pro 4.1 DPP only sends VMware API calls and SSH commands. No Windows proxy servers are needed.

A maximum number of simultaneous backup jobs The use of SAS disk drives are preferred, being about 30% faster than SATA disk drives. External USB drives are the slowest. vRanger Pro 4.1 DPP configuration settings are global for the entire product and so must be set to accommodate your slowest re positories. This is why providin g a mix of external USB drives and SAS drives in your environment is not recommended. vRanger Pro 4.1 DPP will not be faster than your slowest repository. If you get CIFS errors or iSCSI errors, lower your initial configuration settings:

Maximum number of tasks running off a LUN = 3 Maximum number of tasks running off a host = 1 Maximum number of tasks running per repository = 3. If you do not get any errors, then increase tasks per repository by 1.

Acronyms SAS: Ser i al Att ached SCSI SATA: Serial Advanced Technology Attachment SCSI: Small Computer Serial Interface USB: Universal Serial Bus

• Configuration Best Practices (2a) Wh en per f orm i ng b ack ups,

Configuration Best Practices (2a)

Wh en perform ing b ack ups, if you are experiencing slow responses t imes or repository errors, t h en as part of your troubleshooting, eliminate vRanger Pro 4.1 DPP entirely from the picture.

For an ESX serverrepository combination experiencing problems, do a simple ping test from the ESX service console to the repository and note the response time.

Success:

Your response times should be approx. 1 ms (milliseconds) or less. The ESX host and repository should be on the same IP subnet.

Problem1:

If your response time is in the 50 60 ms range, then you are probably crossing one or more routers and/or firewalls. That is a problem because 1) your response time is so slow and 2) the excessive CPU/memory loading on the routers/firewalls as multiple GBs of backup data pass through them. All backup products generate a lot of traffic and it is best to avoid passing that traffic through routers and firewalls.

Problem 2:

If your response time is > 100 ms (e.g., 200 ms), then you may also experience TCP/IP timeouts. Are you crossing a WAN (wide area network)? Crossing a WAN with multiple GBs of backup traffic will guarantee poor performance.

1 Taken from Vizioncore Knowledgebase: http://www.vizioncore.com/support/knowledgebase/index.php.

• Configuration Best Practices (2b) Wh en per f orm i ng b ack ups,

Configuration Best Practices (2b)

Wh en perform ing b ack ups, if you are experiencing repository errors, t h en as part of your trou blesh oot ing, eliminate vRanger Pro 4.1 DPP entirely from the picture.

For an ESX serverrepository combination experiencing problems, do a simple read/write test from the ESX service console to the repository by mounting a share on the ESX host and then using the Linux touch command to create new, empty files.

Success:

You should be able to mount the CIFS share on the ESX host and then successfully run the touch command.

Problem1:

If the mount fails, confirm that your share has Full Control share permissions and a minimum of Modify NTFS folder permissions. Consider trying Full Control NTFS folder permissions.

Problem2:

If the touch fails, confirm that your share has Full Control share permissions and a minimum of Modify NTFS folder permissions. Consider trying Full Control NTFS folder permissions.

1 Taken from Vizioncore Knowledgebase: http://www.vizioncore.com/support/knowledgebase/index.php.

• Configuration Best Practices (3) C ons id er creat i ng a d e

Configuration Best Practices (3)

Consid er creat ing a d edicated networ k to conta in your b ack up tra ffic t h at goes b etween t h e ESX h osts an d the repositories. The vRanger Pro 4.1 DPP server and each ESX host would have two nics (network interface cards).

The first nic would connect each ESX host’s service console1 and vRanger Pro nic1 to the VMware vCenter and to the VM traffic. The second nic would be dedicated to transferring backup traffic from the ESX hosts to the repositories. The vRanger Pro 4.1 DPP server’s second nic would also be connected to the backup network.

Note: For the backup network, fibre nics are preferred and will provide better throughput than 1Gb/sec Ethernet nics.

Other Configuration Best Practices • vR anger P ro 4 .1 DPP can b e

Other Configuration Best Practices

vRanger Pro 4 .1 DPP can b e on a VM or p h ysica l server. It d oesn ’ t matter.

Reason: The vRanger Pro 4.1 DPP server does not handle any backup traffic so it is acceptable to place

vRanger Pro 4.1 DPP on a VM, as long as the VM meets the requirements (see the next bullet).

vRanger Pro 4.1 DPP meets the hardware and software requirements 1 :

Dual CPU, 2GB RAM, 4GB free disk space (min.), a Gigabit Ethernet nic. 64 bit Windows Server 2003 for large environments (200+ ESX hosts). Reason: vRanger Pro 4.1 DPP running on 32 bit Windows servers is fine for most customers. Large customers with 200+ ESX servers should consider a 64 bit server.

Consider a 64 bit Server for the Repository

Reason: 64 bit servers can move twice the data as 32 bit. High speed CPU, PCI bus, and disk recommended.

The ESX Service Consoles are properly configured 1

Increase Service Console CPU Reservation to 1500MHz; Increase Service Console RAM to 800MB. Reason: vRanger Pro 4.1 DPP uses snapshots prior to doing a backup and the increased resources for the service console help ensure snapshot success. These settings are also recommended for vRanger Pro 3.x.

vRanger Pro and the repository should be on separate servers

Reason: If the Repository gets overloaded with data from backups, then vRanger Pro 4.1