Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- 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
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- 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.