Upgrading shares from v2.x to v3.x – HP StorageWorks Enterprise File Services WAN Accelerator User Manual

Page 107

Advertising
background image

HP S

TORAGE

W

ORKS

EFS WAN A

CCELERATOR

M

ANAGEMENT

C

ONSOLE

U

SER

G

UIDE

107

2 C

ONF

IGUR

ING

TH
E

HP

EF

S

WA

N

A

CC
EL
ERA

T

O

R

5. Click Syncing Enable to download the initial copy of the share from the origin

server to the HP EFS WAN Accelerator and to configure the share for automatic
synchronization.

6. Click Sharing Enable to make the share available to end users for mounting. End

users will be able to read the share by mapping to the mounted share (for example,
\\HP EFS WAN Accelerator\share1).

After you enable sharing, you can map this share from your machine by typing:
\\<HP EFS WAN Accelerator or primary interface IP address>\<name of
share>

7. Click Save to write your changes to disk or Cancel to cancel your settings.

NOTE: When performing the initial synchronization, or when changing large amounts of data,
your bandwidth utilization and other graphs may show pockets of inactivity. This is by design.

Upgrading Shares
from V2.x to V3.x

When you upgrade to v3.x software, all your existing shares will be running as v2.x
shares.

In v3.0 you no longer need to install the HP EFS Remote Copy Utility (RCU) service
on the server for synchronization purposes—all RCU functionality has been moved to
the HP EFS WAN Accelerator.

If you have legacy shares (that is, shares created with Version 2.x software), you must
upgrade your v2.x shares to v3.x shares in the Management Console.

IMPORTANT: HP recommends that you convert your v2.x shares to v3.x shares. HP

recommends you do not configure a mixed system of PFS shares, that is v2.x shares and v3.x

shares.

When you upgrade your shares you must specify the remote path for the share. The
format depends on the path name:

‹

If you created your share with v2.x software, this value represents the name of the
Windows server where the RCU is running. If the remote path share contains a
drive letter, then you must provide a new remote path in UNC format that points
to the same directory. For example, if the remote path was c:\data\eng on a server
called granite. To upgrade, you must log in to granite, and make c:\data\eng a
shared directory, with the name eng. In the Management Console, you specify
\\granite\eng as your new remote path for the v3.x upgrade.

‹

If the remote path share is in UNC format, you simply copy that path to the
Remote Path field.

Advertising
This manual is related to the following products: