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
Setting up files to exclude from an episodic replication unit
Once you have set up the file systems you want to replicate, you can define a set of directories or files to exclude from an episodic 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> episodic exclunit create command to name the excluding unit and configure the directories and files you want to exclude from an episodic replication. The excluding unit you create can be used in multiple episodic replication jobs. A single excluding unit can span across multiple directories.
Use the Replication> episodic job exclude command to add the excluding unit to a episodic 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> episodic exclunit add_entry, Replication> episodic exclunit modify_entry, and Replication> episodic 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> episodic job show command to show which excluding units are configured for a job. Use the Replication> episodic exclunit show command to show the names and contents of all excluding units that are defined for the cluster.
Use the Replication> episodic 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 an episodic 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 episodic replication and it cannot be a parent directory of the episodic replication. For example, if a episodic 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 episodic replication).
By default, Veritas Access excludes some common directories and files from all episodic 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> episodic 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 episodic replication. For example, an episodic replication job that contains an fs1
episodic 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> episodic 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 an episodic replication.
- To confirm the creation of the excluding unit enter the following:
Replication> episodic exclunit show verbose
You can use the Replication> episodic exclunit add_entry, Replication> episodic exclunit modify_entry, Replication> episodic exclunit remove_entry, and Replication> episodic exclunit destroy commands to manage your excluding units.
Note:
The Replication> episodic exclunit add_entry, Replication> episodic exclunit modify_entry, Replication> episodic exclunit remove_entry, and Replication> episodic exclunit destroy operations are not allowed for excluding units that are included in any job definitions.