HP Enterprise File Services WAN Accelerator manual How Does PFS Work?

NOTE: When you configure a share, a text file (._rbt_share_lock. txt), is created on the origin server that keeps track of which HP EFS WAN Accelerator owns the share. Do not remove this file. If you remove the ._rbt_share_lock. txt file on the origin file server, PFS will not function properly.

‹Stand-Alone Mode. Provides the client read-write access to data on a remote HP EFS WAN Accelerator. For example, if you want to load temporary data from a remote client to the remote HP EFS WAN Accelerator that does not need to be backed up at a data center, you can create a share in Stand-Alonewithout a remote path. A Stand-Aloneshare with a remote path is initially populated with data from the origin server after which changes and/or new data created on the share are not sent back to the origin server.

‹Global Mode. HP EFS WAN Accelerator optimization without PFS enabled.

How Does PFS Work?

To synchronize the data volumes, the HP EFS WAN Accelerator communicates to the HP EFS RCU running on the origin server. If the origin server is a non-Windows file server and cannot run the HP EFS RCU, then the HP EFS RCU can be run on a Windows server with write-access, to the origin server.

PFS provides Windows file service in the HP EFS WAN Accelerator at a remote site. The HP EFS WAN Accelerator is configured as a Domain Member Server. Data volumes at the data center are configured explicitly on the proxy file server and are served locally by the HP EFS WAN Accelerator. As part of the configuration, the data volume including the Access Control Lists (ACLs) from the origin server are copied on to the HP EFS WAN Accelerator. PFS allocates a portion of the HP EFS WAN Accelerator data store for users to access as a network file system.

PFS in the HP EFS WAN Accelerator allows a Domain Controller (DC) to authenticate users accessing its file shares. The DC can be located at the remote site or over the WAN at the main data center. The HP EFS WAN Accelerator must be configured as a Member Server in the Windows 2000, or later, Active Directory Services (ADS) domain. Domain users are allowed to access the PFS shares based on the access permission settings provided for each user.

86 8 - PROXY FILE SERVICE DEPLOYMENTS