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
About buckets and objects
The Object Store server consists of a collection of objects. The container of an object is known as a bucket. In Veritas Access Object Store, the buckets are stored on file systems as directories and object are stored as files.
Buckets and objects are resources which can be managed using the APIs.
Once the Object Store Server is configured, you can create bucket and objects and perform the required operations.
Veritas Access supports the following methods for accessing the buckets and the objects:
Path-style method
Virtual-hosted-style method
When using the virtual hosted-style method, the bucket_name.s3.cluster_name should be DNS resolvable.
See the objectaccess_bucket(1) manual page for more information.
See the objectaccess manual pages for all of the Veritas Access Object Store server operations that can be performed.
Buckets are created by S3 clients by calling the standard S3 APIs to the Veritas Access S3 server. For creating a bucket, you need the endpoint of the Veritas Access server, access key, and the secret key. The endpoint of the Veritas Access Object Store server is s3.cluster_name:8143.
The Veritas Access Object Store server can also be accessed using the fully qualified domain name:
s3.cluster_name.fqdn:8143
Make sure that you associate one (or more) of the VIPs of the Veritas Access cluster to s3.cluster_name.fqdn in the client's DNS server.
Table: Object and bucket restrictions describes the restrictions enforced by the Veritas Access Object Storage Server. Configure your S3 clients within these limitations to ensure that Veritas Access works correctly.
Table: Object and bucket restrictions
Description | Limit |
---|---|
Maximum recommended parallel threads | 10 |
Maximum number of buckets per file system with fs_sharing enabled | 10,000 |
Maximum number of objects per file system | 1 billion |
Maximum supported size of an object that can be uploaded using a single PUT | 100 MB |
Maximum number of parts supported for multipart upload | 10,000 |
Maximum supported size range of an object that can be downloaded using a single GET | 100 MB |
Maximum number of grantees supported for setting ACL on buckets/objects | 128 |