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
Use cases for configuring the Object Store server
You can configure the Object Store server depending on different use cases.
Use Case 1: Large number of objects per bucket are required.
The admin can configure a default pool without using the fs_sharing option.
The file system is not shared across buckets. A bucket can have large number of objects. The choice of file system sharing limits the number of buckets created.
Use Case 2: Admin needs large number of buckets but does not expect large number of objects per bucket.
The admin can create a group in its authentication server and configure this group in Object Store using the objectaccess> group set command.
The grouping provides options like choosing the disk pool to use, file system type, file system sharing, file system size, other file system options.
The admin can use the fs_sharing option to configure the Object Store server to share a file system across all buckets that are created by a user of that particular group.
The file system sharing allows the Object Store server to create a large number of buckets but limits the total number of objects present across the bucket.
Use Case 3: Admin wants to control the file system used for a bucket.
The admin has to pre-create the required file system using the storage> fs commands.
The admin can use the objectaccess> map command to map a directory of the existing file system as a bucket for a particular user.