Dell DX6000G Setup And Configuration Manual
  1. Manuals
  2. Brands
  3. Dell Manuals
  4. Software
  5. DX6000G
  6. Setup and configuration manual

Dell DX6000G Setup And Configuration Manual

Dx storage cluster file server (cfs) setup and configuration guide version 2.6
Hide thumbs Also See for DX6000G:
Table of Contents

Quick Links

See also: Hardware Owner's Manual, User Manual
DX Storage Cluster File Server (CFS)
Setup and Configuration Guide
Version 2.6
Table of Contents
loading

Related Manuals for Dell DX6000G

Summary of Contents for Dell DX6000G

  • Page 1 DX Storage Cluster File Server (CFS) Setup and Configuration Guide Version 2.6...
  • Page 2 DX Storage Cluster File Server (CFS) Setup and Configuration Guide: Version 2.6 Copyright © 2011 Caringo, Inc. All Rights Reserved. No part of this document may be reproduced, transmitted, or transcribed without the written consent of Caringo, Inc.

  • Page 3: Table Of Contents

    Table of Contents 1. Welcome to DX Storage CFS ....................1 1.1. Overview of DX Storage CFS ..................1 1.2. About this Document ....................1 1.2.1. Audience ....................... 1 1.2.2. Scope ......................1 2. Installation and Guided Configuration ..................2 2.1.

  • Page 4: Welcome To Dx Storage Cfs

    Chapter 1. Welcome to DX Storage CFS 1.1. Overview of DX Storage CFS DX Storage Cluster File Server (CFS) is a native DX Storage application that presents a DX Storage cluster as a standard Linux file system, enabling the use of DX Storage by software that uses a file system.

  • Page 5: Installation And Guided Configuration

    Chapter 2. Installation and Guided Configuration 2.1. Requirements 2.1.1. Operating System DX Storage CFS has been developed and tested with 64-bit Red Hat Enterprise Linux 6.0; other RHEL versions or Linux distributions are not currently supported. Subsequent installation instructions will assume a pre-installed RHEL environment with either internet connectivity or an alternately configured RHEL yum repository for use in installing required 3rd party packages.

  • Page 6: Installation Steps

    directories critical to recovering from a failure. Specifically, the following 3 directories should be mounted with 'nodelalloc': mount /dev/sdxx /var/lib/dht -o rw,nodelalloc,user_xattr mount /dev/sdxx /var/cache/cns -o rw,nodelalloc,user_xattr mount /dev/sdxx /var/spool/cfs -o rw,nodelalloc,user_xattr 2.2. Installation Steps The following steps are necessary to install DX Storage CFS. •...
  • Page 7 # cns-admin Note: Please make sure DX Storage is online and reachable prior to configuring the new name space. cns-admin will prompt for the following values: Log facility. Enter the logging facility to use. The default value is syslog. Log filename. If the file logging facility was selected, enter the filename and location of the logfile.
  • Page 8 Cluster secondary node address: Enter the IP address or hostname for a second DX Storage node in the target cluster for redundancy. The target cluster must be the same as the one configured for all CFS mounts. Secondary node SCSP port: Enter the port the secondary DX Storage node uses for SCSP communications.

  • Page 9: Configuring Dx Storage Cfs And Its Mountpoints

    Note The name space must remain online at all times to ensure CFS can obtain the needed file system information. If CFS cannot connect to the name space, it will start throwing permission denied errors and block new file writes. 2.2.3.
  • Page 10 Syslog facility. If the syslog option was selected, enter the facility to log to. The default value is local4. Configuration of a remote syslog host must be done in the syslogd configuration file. Log level. Enter the minimum level of log messages to record. The default value is info. Debug is not recommended unless explicitly requested as part of a support investigation due to the amount of disk space consumed that will not then be available for core processes.

  • Page 11: Post-Configuration File System Options

    Cluster primary node address: Enter the IP address or hostname of a DX Storage node in the target cluster. The target cluster must be the same as the one configured for the Cluster Name Space (CNS). Primary node SCSP port: Enter the port the DX Storage node uses for SCSP communications.

  • Page 12: Deleting A Mountpoint

    2.2.4.1. ACLs The cfs-admin mkfs utility does not by default enable Access Control Lists or ACLs. ACLs provide more fine-grained file and directory access control than the basic user, group, owner permissions and can be very useful in complex permission scenarios. For more information on ACLs functionality and syntax, please refer to the manpage.

  • Page 13: Upgrading From Version 2.5

    2.4.3. Upgrading from Version 2.5 Version 2.5 Red Hat installations can upgrade to 2.6 by stopping all services, installing the new version and then restarting services. After copying the 2.6 distribution file to the server and unzipping it, run the following commands as root: Note Any configuration file backups previously taken for disaster recovery purposes must be discarded and a new backup taken, as previous configuration files are not compatible...

  • Page 14: Restoring Cfs

    descriptive error is not passed through to the client. Check the syslog for a full description of the possible errors if the uninstall is unsuccessful. 2.6. Restoring CFS Should a CFS server ever fail or need to be repurposed, all persisted data can be restored or moved onto a new CFS server by configuring the server as you would a new server but then replacing the CNS rootUUID with the previously configured one.

  • Page 15: Running And Managing Dx Storage Cfs

    Chapter 3. Running and Managing DX Storage CFS 3.1. Starting DX Storage CFS and CNS The Cluster Name Space should always be started prior to CFS. The name space can be started using the following command: $ /etc/init.d/caringo-cns start CNS will fail to start and print an appropriate error message if one of several critical configuration parameters is missing or invalid.

  • Page 16: Timescapes

    After CFS has been stopped, CNS may also be stopped using the following command: $ /etc/init.d/caringo-cns stop 3.3. Timescapes The DX Storage CFS Timescape continuous snapshot feature allows an administrator to mount a historical, read-only view of a file system at any past time, providing a mechanism to both view and/ or copy previous versions of files that might otherwise be lost.

  • Page 17: Deleting A Timescape Mount

    start without these directories. You will also be asked if you would like to mount the configured mountpoint immediately. Once mounted, you will be able to view the specified CFS share at the time in the past specified by your configured Timescape time. All timescape mounts are read-only but you may copy a deleted file from a timescape mount to an active, current mount to recreate the file in the present.

  • Page 18: Cfs-Grab

    Argument Definition and usage -p PORT or --port=PORT SCSP Port for the configured DX Storage node (default=80) -r ROOTUUID or --uuid=ROOTUUID The CNS rootID you received during initial configuration -c CFSID or --cfsid=CFSID The CFSID of the share for which you want to report -l list or --list=LIST Option that returns the list of CFSIDs in the...

  • Page 19: Cfs-Loglevel

    sudo cfs-admin config The script will prompt for the CFSID you wish to modify and then display the same prompts from initial configuration but with the current configuration displayed for each prompt. If you do not wish to modify a particular parameter, simple press enter and the current value will remain in place. Some parameters like the configured namespace that might strand or corrupt data are view only.

  • Page 20: Custom Metadata

    • Castor-CFS-FileId: the filesystem id for the file in the CFS name space • Castor-CFS-Uid: the file's user id at the time it was stored • Castor-CFS-Gid: the file's group id at the time it was stored • Castor-CFS-Mode: the file's permission mode in decimal at the time it was stored The mechanisms to add both custom metadata and life cycle retention policies to files stored in DX Storage via DX Storage CFS are outlined in the sections below.

  • Page 21: Dx Storage Lifecycle Policies

    # cfs-admin metadata --delete --name=Department --value=Legal /mnt/legal 3.6.2. DX Storage Lifecycle Policies In addition to custom metadata, the 'cfs-admin policy' utility allows a root user to administer the content storage constraint policy for newly created files that are ready to be stored in DX Storage (last file close plus 5 seconds).
  • Page 22 # cfs-admin policy --modify --span=2y --lifepoint=1 /mnt/legal Finally, to delete a policy, the 'delete' action can be executed as follows by specifying which lifepoint to delete. If the specified lifepoint does not exist, the system will return a 'No such lifepoint' error. If more than one lifepoint is in effect, you should be sure to validate the remaining lifepoints printed after the delete to ensure the end-to-end lifecycle policy is as intended.

  • Page 23: Temp And Logging Space Configuration

    Appendix A. Temp and Logging Space Configuration Every file that is written to or read from the DX Storage cluster will be cached in the location specified for the spooler directory during the installation process. The spooler directory is integral to the internal function of DX Storage CFS and should never be manually manipulated, particularly while CFS is actively running.

This manual is also suitable for:

Dx storage cluster file server

Table of Contents