Understanding the CommCell Console
Managing File Access Time when Unix File System iDataAgent is also installed
Delete the File after Archiving
Replace File With a Stub After Archiving
Prune the Archived Files (Storage Reclamation)
Configuring for Optimized Stub Recall
Extend the Persistent Pipeline Timeout
Limit the Number of Persistent Pipeline Threads During Recoveries
Stub Recall from Any Available Data Copy
Filtering Files From Archiving
Manually Filtering Files from Archiving
Manually Including Files for Archiving
Setting the Maximum Number of Stubs in a Recall Job (Recall Throttling)
Configuring Archiving for X9000 IBRIX
Configuring Archiving for Lustre File System
Modifying an ArchiveSet or Subclient
Deleting an Agent, ArchiveSet or Subclient
In order to perform archiving operations, you need to initially configure archiving rules. Archiving rules specify the criteria for the type of data to be archived. You can configure these rules on a requirement basis.
You can set rules to archive files based on the last accessed date of each file within the volume or folder/directory. Files older than the specified date will be archived.
Archiving files based on file access times has special considerations. Ordinarily the action of backing up a file using the File System backup agent will cause the file access time to change to the time of the backup. This action may have an undesired effect on the archiver agent if you want to archive files based on access time.
To workaround this situation, you should either use Classic File Scan with the Preserve File Access Time option selected as the scan method OR a software snapshot (VSS or Qsnap) to accomplish the backup. If the software snapshot fails (i.e. VSS service unavailable or unable to quiesce the volume), you can use the Open Files Failure Actions dialog box to select the desired action to be performed.
You can also set rules to archive file based on the last modified time. Files that were modified earlier than the specified time will be archived.
You can also set archiving rules to archive files depending on the file size. If a file size within a scanned volume or folder/directory is in between the specified size limit, it will get stubbed.
The backed up files can be stubbed based on the available free space on the volume. Volumes are periodically checked for available space. If the free space is lesser than the specified low watermark value, the archiving operation begins. The stubbing process stops once it reaches the specified high watermark value.
|
By default files that are less than or equal to the file system block size are skipped from archiving. To archive all the files follow the steps given below:
|
For an archiving operation, you can set certain stub rules to manage the archived files.
You can choose to delete the file after an archiving operation.
|
By default, during an archive operation, the file is replaced with a stub. However, if required, you can also set this manually from the Subclient Properties window.
|
By default, the stubs are pruned along with the media. However, you can set the number of days after which the stubs will be pruned.
|
It is recommended to leave the persistent pipeline open for longer periods of time to cache important information for subsequent recall attempts. By default this timeout is set to 24 hours.
Once this key is activated, services must be restarted on the client computer. |
You can increase the number of persistent pipeline threads allowed for recoveries, thereby potentially improving stub recall speed. The recommended number of threads would be the number of Media Agents, which could possibly be used for recoveries. By default two threads will be used. Therefore if more than two Media Agents are potential targets for stub recalls increase the number of threads accordingly as follows:
Once this key is activated, services must be restarted on the client computer. |
By default if the primary copy of the data is unavailable the stub recall will fail. However you can configure to trigger stub recall from an alternate data copy as follows:
|
Prior to archiving the files, you can set filters to prevent specific type of files from being archived. Filters can also be used to exclude certain system-related files and database application files which consistently fail during a archive operation and are not integral to the operation of the system or application.
Files with extensions *.a, *.ksh, *.csh, *.sh, *.lib, and *.so are automatically filtered out of subclient content by default. Similarly, files in the following directories are also skipped from archiving on all Unix platforms.
You can manually set filters on selected file types, folders or files to be excluded from archiving. For example if you specify *.txt in the filters then all the text files will be excluded from being archived.
|
When excluding files from archiving, you can also provide exceptions to the data that you are excluding. For example, if you want to exclude from your migration archive operation all the files in the /Ops directory except the Maintenance file, you can add a subclient filter to exclude the /Ops directory from being archived and also add a corresponding subclient filter to allow the Maintenance file to be archived.
|
The maximum number of simultaneous stub recalls can be limited to a specified amount of time. This will not only optimize performance but can also prevent the inadvertent recovery of a large number of files.
|
For X9000 IBRIX , by default the stubs are recalled during the data tiering process, which moves the files and the data stubs from one storage tier to another based on pre determined parameters. However you can configure the sTranProcName registry key to seamlessly migrate data stubs from one storage tier to another without triggering a stub recall. The steps to configure the key are as follows:
|
Perform the following to configure archiving for Lustre file system:
|
After recalling the files, you can re-archive the recalled files by preserving them in a stub cache. The recalled file will be re-archived from the cache if the file meets the archiving rules and has not been modified after the recall. The following registry keys allow you to set the stub cache and re-stub the recalled files from the cache memory.
nUSE_STUB_CACHE | This key allows a file to be re-stubbed after recall by preserving it in cache memory. |
dSTUB_CACHE_ROOT | By default the stubs are cached under , /opt/calypso/stubcache folder. Use this key to specify a different location of the root folder for the File Archiver stub cache. |
The following table describes the properties that can configured from the agent, backup set/archive set, and subclient levels.
Option | Description | Related topics |
Configure Activity Control |
You can enable backup and restore operations from the agent and subclient level.
However, you can enable recovery operations only from the agent level. Agent Level:
Subclient Level:
|
Refer to Activity Control. |
Release License | You can release a license for client, MediaAgent and
agent. If releasing a license is successful, the tree element is dimmed
and available for deletion.
|
|
Change Storage Policies | You can modify the storage policies in any of the following situations.
You can change the storage policies from the subclient level.
|
Refer to Storage Policies. |
Rename Backup Set/Archive Set | You can rename an existing Backup Set/Archive Set.
|
|
Rename a Subclient | You can rename an existing subclient.
|
|
Configure Data Transfer Options |
You can efficiently configure the available resources for transferring data secured
by data protection operations from the subclient level. This includes the following:
You can configure the data transfer options.
|
Refer to Data Compression and Network Bandwidth Throttling. |
View Data Paths |
You can view the data paths associated with the primary
storage policy copy of the selected storage policy or incremental storage
policy. You can also modify the data paths including their priority from
the subclient level.
|
|
Configure account for Pre/Post Processing of Data Protection |
You can add, modify or view Pre/Post processes for the
subclient. These are batch files or shell scripts that you can run before
or after certain job phases.
|
Refer to Pre/Post Processes. |
Configure User Security |
You can configure user security from the agent, backup set/archive set or subclient
levels.
You can perform the following functions:
|
Refer to User Administration and Security. |
Enable/Disable Data Encryption |
You must export the pass-phrase to the local computer before performing
a stub recovery operation of encrypted data.
You can enable data encryption from the subclient level. Encryption must be enabled at the client level prior to configuring any
instances residing on that client.
|
Refer to Data Encryption. |
View Software Version and Installed Updates |
The Version tab, at the Agent level displays the
software version and post-release service packs and updates installed for
the component.
|
|
CommCell Configuration Report |
The CommCell Configuration Report provides the properties of the
CommServe, MediaAgents, clients, agents, SRM agents, subclients, and
storage policies within the CommCell based on the selected filter
criteria.
|
Refer to CommCell Configuration. |
Archive Job Summary Report |
The Archive Job Summary Report provides the detailed archive information
such as the start and end time (or current phase), the total size of the
archive job, the elapsed time, the transfer time, the throughput, the
number of objects archived, the amount of data, the failed folders and
files, content indexing usage and failures (if any), and the filters
used for the archive.
|
Refer to Archive/Compliance Archive Job Summary Report |
The following sections describe the steps involved in deleting an agent, archive set or subclient.
When you delete an instance or backupset, the associated data is logically deleted and you can no longer access the corresponding data from CommCell Console for recovery purposes. Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity. |
You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.
This operation will permanently delete the data backed up from this level and it cannot be restored.
Consider the following before deleting a Backup Set:
Click No to cancel the deletion and retain the Backupset, or click Yes to continue the deletion.
Consider the following before deleting a subclient:
Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.