Veritas Access 7.3 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
- About Flexible Storage Sharing
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your 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 Veritas Access to work with Oracle Direct NFS
- Configuring an FTP server
- Configuring your NFS server
- Section V. Managing the Veritas Access Object Store server
- Section VI. Monitoring and troubleshooting
- Section VII. 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 VIII. Configuring cloud storage
- Configuring the cloud gateway
- Configuring cloud as a tier
- About policies for scale-out file systems
- Section IX. 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
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring replication
- Replication job failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring Veritas Access with the NetBackup client
- Section XI. Reference
Setting up files to exclude from a replication unit
Once you have set up the files systems you want to replicate, you can define a set of directories or files to exclude from a replication unit. This step is optional. The exclunit entry has higher priority over the repunit entry. If any file name matches the exclunit entry, the file is not replicated to the target.
To work with exclusion units:
Use the Replication> exclunit create command to name the excluding unit and configure the directories and files you want to exclude from a replication. The excluding unit you create can be used in multiple replication jobs. A single excluding unit can span across multiple directories.
Use the Replication> job exclude command to add the excluding unit to a replication job. You cannot add an excluding unit to a job that is active. You must disable the job first.
You can use the following commands: Replication> exclunit add_entry, Replication> exclunit modify_entry, and Replication> exclunit remove_entry to make changes to an excluding unit, provided the excluding unit you want to modify is not included in any job definitions.
Use the Replication> job show command to show which excluding units are configured for a job. Use the Replication> exclunit show command to show the names and contents of all excluding units that are defined for the cluster.
Use the Replication> exclunit destroy command to permanently delete the excluding unit. You can only destroy an excluding unit if the excluding unit you want to destroy is not included in any job definitions.
If a replication is defined for a directory, an excluding unit should be a subset of that directory. The excluding unit cannot be the same directory as the replication and it cannot be a parent directory of the replication. For example, if a replication is configured for fs1/dir1/dir2
, a valid exclusion could be dir1/dir2/file
or dir1/dir2/dir3
, but not /dir1
(the parent directory for the replication).
By default, Veritas Access excludes some common directories and files from all replication units. These directories and files include:
lost+found
.placement_policy.xml
quotas
quotas.grp
quotas.64
quotas.grp.64
In addition, you can use the Replication> exclunit commands to specify additional directories and files to exclude.
The directories and files you specify for an excluding unit are applied based on the overall definition of the replication. For example, a replication job that contains an fs1
replication unit and an dir3
excluding unit, replicates all the files in fs1
, except for the files in fs1/dir3
.
To create an excluding unit:
- To create an excluding unit, enter the following:
Replication> exclunit create exclunit_name exclunit_entry[,exclunit_entry,..]
exclunit_name
Enter the name of the excluding unit.
exclunit_entry
Enter the comma-separated list of directories and files you want to exclude from a replication.
- To confirm the creation of the excluding unit enter the following:
Replication> exclunit show verbose
You can use the Replication> exclunit add_entry, Replication> exclunit modify_entry, Replication> exclunit remove_entry, and Replication> exclunit destroy commands to manage your excluding units.
Note:
The Replication> exclunit add_entry, Replication> exclunit modify_entry, Replication> exclunit remove_entry, and Replication> exclunit destroy operations are not allowed for excluding units that are included in any job definitions.