Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Configuring storage pools
A storage pool is a group of disks that Access Appliance uses for allocation. Before creating a file system, you must create a storage pool.
To create the storage pool used to create a file system
- List all of the available disks, and identify which ones you want to assign to which pools.
Storage> disk list
- To create a storage pool, enter the following:
Storage> pool create pool_name disk1[,disk2,...] [isolated=yes|no]
pool_name
Specifies what the created storage pool will be named. The storage pool name should be a string.
disk1, disk2,...
Specifies the disks to include in the storage pool. If the specified disk does not exist, an error message is displayed. Use the Storage> disk list command to view the available disks.
Each disk can only belong to one storage pool. If you try to add a disk that is already in use, an error message is displayed.
To specify additional disks to be part of the storage pool, use a comma with no space in between.
isolated=yes|no
Optional. Specifies whether or not the storage pool is isolated from other storage pools. Isolating the storage pool means that the configuration information is not shared. By default, storage pools are not isolated.
To add a set of disks to a logical pool
- To add a set of disks to a logical pool, enter the following:
Storage> pool adddisk pool_name disk1 [,disk2,...]
Where pool_name specifies the name of the storage pool to which the disks have to be added.
disk1, disk2,.. specifies the disks to be added to the pool.
To list your pools
- To list your pools, enter the following:
Storage> pool list
If a node is down, the Storage> pool list command shows local disks of that node.
To rename a pool
- To rename a pool, enter the following:
Storage> pool rename old_name new_name
old_name
Specifies the name for the existing pool that will be changed. If the old name is not the name of an existing pool, an error message is displayed.
new_name
Specifies the new name for the pool. If the specified new name for the pool is already being used by another pool, an error message is displayed.
To destroy a storage pool
- Because you cannot destroy an unallocated storage pool, you need to remove the disk from the storage pool using the Storage> pool rmdisk command prior to trying to destroy the storage pool.
If you want to move the disk from the unallocated pool to another existing pool, you can use the Storage> pool mvdisk command.
- To destroy a storage pool, enter the following:
Storage> pool destroy pool_name
Where pool_name specifies the storage pool to delete. If the specified pool_name is not an existing storage pool, an error message is displayed.
If a node is down temporarily, it is not a good practice to destroy a storage pool that contains local disks of that node.
Note:
You cannot destroy the last non-isolated pool if isolated pools exist.
To mark a disk as a spare disk
- To mark a disk as a spare disk and add it to a pool which can be later used for hot relocation, enter the following:
Storage> pool markdiskspare pool_name disk1 [, disk2,...]
Where pool_name specifies the name of the storage pool to which the disks have to be added.
disk1, disk2,.. specifies the disks to be marked as spare.
In case of failure of a disk or a plex, the affected sub disks are relocated to disks designated as spare disks.
To remove the spare disk flag set on a disk
- To remove the spare disk flag set on a disk by the Storage> pool markdiskspare command, enter the following:
Storage> pool removediskspare pool_name disk1 [, disk2,...]
Where pool_name specifies the name of the storage pool to which the disks belong.
disk1, disk2,.. specifies the disks from which the spare disk flag has to be removed.
To list free space for pools
- To list free space for your pool, enter the following:
Storage> pool free [pool_name]
Where pool_name specifies the pool for which you want to display free space information.
If a specified pool does not exist, an error message is displayed.
If pool_name is omitted, the free space for every pool is displayed, but information for specific disks is not displayed.