Installation guide

Acopia Networks, Inc.
• Time Windows for Log Collection – You can focus the collection of log messages by choosing an
optional start time and end time. Refer to the documentation for the CLI command, collect logs.
• Monitoring for CIFS-Client Activity – A new CLI command, show cifs-service client-activity,
shows details about a CIFS-client connection to the ARX, as well as the proxy connections from the
ARX to the filers behind it.
2.5.0 Features
This section applies to installations that are upgrading from Release 2.4.3.
Release 2.5.0 offered the following new features, also included in this release:
• Faster Imports into Managed Volumes – In previous releases, managed volumes divided their
imports into multiple scans, including a directory scan and a longer file scan. Volumes run the scans
simultaneously in this new release. Additionally, a managed volume does not spend time protecting its
metadata during the import; metadata protection is rarely necessary until the volume is running. Both
options are configurable. Managed-volume imports are significantly faster with these options enabled,
along with some other internal optimizations.
• Support for CIFS subshares and their ACLs – This release supports CIFS subshares and their share-
level ACLs. A subshare is a CIFS share that is contained inside another share. The top-level share
often has a different share-level Access Control List (ACL) than each of its subshares. By default, a
volume always accesses directories through the top-level share, even when a client connects to a
subshare on the front end. The volume connects to the top-level share, subjecting the client to the ACL
there, then descends to the desired subdirectory. With this new feature, a CIFS service and CIFS
volume can pass a client from a front-end subshare directly to the corresponding back-end subshare.
The client therefore uses the subshare’s ACL.
• No Client Restrictions in Multi-Protocol (NFS and CIFS) Volumes – Clients of a multi-protocol
managed volume can now create directories with any name. In previous releases, volumes did not
permit any names that resembled filer-generated names (FGNs, such as “myDir~1”).
• Ability to Migrate a Metadata Share – There is a new option to migrate a managed volume’s
metadata from one dedicated share to another.
• Firmware Upgrades – You can use a new CLI command, firmware upgrade, to install any new
firmware bundled with the latest software release. This command is documented in the software-
upgrade chapter of the CLI Reference.
Automatic Upgrades for Multi-Protocol Volumes
A multi-protocol volume keeps additional metadata about its files and directories in the 2.5.0+ releases.
The volume typically writes this information as it imports the volume’s shares; this is not possible if you
upgrade a previously-imported volume from Release 2.4.3. An automatic-upgrade process rewrites the
metadata after the software upgrade.
The ARX runs an upgrade process in the background. It begins after the ARX boots with the 2.5.0+
software; if the ARX has a redundant peer, the upgrade begins after both peers are running the new release.
The upgrade process runs on each multi-protocol volume, one at a time, to minimize CPU and bandwidth
consumption. The process generates one report per volume, which you can access from the CLI with the
7