HP StorageWorks Enterprise File Services WAN Accelerator 3.0.4 Command-Line Interface reference manual (AG421-96004, March 2007)

140 4 - CONFIGURATION-MODE COMMANDS
Version 2. Specify the server name and remote path for the share folder on the
origin file server. With Version v2.x, you must have the RCU service running on a
Windows server—this can be the origin file server or a separate server.
HP recommends you upgrade your v2.x shares to 3.x shares so that you do not
have to run the RCU on a server.
IMPORTANT: If you have shares that were created with v2.x of the HP EFS WAN Accelerator
software, the account that starts the RCU must have write permissions to the folder on the origin
file server. Also, the logon user for the RCU server (which is used for v2.x shares and the share
creation user for version 3 shares must to be a member of the Administrators group, either locally
on the file server (the local Administrators group) or globally in the domain (the Domain
Administrator group).
Version 3. Specify the login, password, and remote path used to access the share
folder on the origin file server. With Version 3, the RCU runs on the HP EFS
WAN Accelerator—you do not need to install the RCU service on a Windows
server.
IMPORTANT: Make sure the users are members of the Administrators group on the remote
share server, either locally on the file server (the local Administrators group) or globally in the
domain (the Domain Administrator group).
IMPORTANT: The PFS share and the origin-server share name cannot contain Unicode
characters. The HP EFS WAN Accelerator Manager does not support Unicode characters.
NOTE: HP recommends that you do not run a mixed system of PFS shares, that is, v2.x shares
and v3.0 shares.
Syntax [no] pfs share configure {local-name <local name>
{version <2> remote-path <remote path> server-name <name> port <port>
interval <seconds> full-interval <seconds> start-time <yyyy/mm/dd hh:mm:ss>
[comment <description>]} |
{version < 3> mode <mode> remote-path <remote path> server-account
<account>
server-password <password> interval <seconds> full-interval <seconds>
start-time <yyyy/mm/dd hh:mm:ss> [comment <description>]}}