Pruning Archived Data for Space Reclamation
Filtering Files From Archiving
Manually Filtering Files from Archiving
Manually Including Files for Archiving
Filtering Files Using Registry Key
Configuring Archiving for IBRIX File System
Archiving rules specify the criteria for the type of data to be archived. You can configure these rules on a requirement basis.
The backed up files can be stubbed based on the available free space on the volume. During a backup job if the free space on the volume is less than this value, files matching the remaining rules will get stubbed.
This configuration will stub files based on the last accessed date of each file within the volume or folder/directory. In case it is older than the number of days specified, the files will get stubbed.
This configuration will stub files based on the last modified date of each file within the volume or folder/directory.
This configuration will stub files based on the file size. If a file size within a scanned volume or folder/directory is in between the two limit values set, it will get stubbed.
By default, the stubs are deleted 730 days from the day of stubbing when you enable the Prune archived items option. However, you can set the number of days after which the stubs will be pruned using the following steps:
Archived data is pruned and secondary storage space is reclaimed based on the stub retention setting and the storage policy cycle - based retention criteria. Running a synthetic full backup can reduce space on the secondary storage for deleted stubs that meet the expiration criteria. Running data-aging can reclaim space on the secondary storage by pruning the expired backup jobs. The following section describes two scenarios for space reclamation:
By default stub retention is set to 730 days from the Stub Rules tab and the Storage Policy retention is set for 2 cycles and 15 days. The following procedure demonstrates the reduction in the secondary storage usage:
1. |
|
![]() |
2. |
The following procedure demonstrates the reclamation of secondary
storage space:
|
In order to reclaim space on secondary storage by completely removing the archived data and their stubs, follow the steps given below:
Pre-requisites
1. | Change the stub retention to a minimum of 1 day from Subclient properties Stub Rule tab.. |
2. | Change the storage policy retention setting to 2 cycles and 15 days. |
3. | Delete the unwanted stubs. |
4 | Perform incremental backup twice to generate two backup cycles. |
5 | Wait for the deleted stubs pertaining to last backup job in the first backup cycle to expire. |
6 | Run synthetic full backup with Check for
Deleted Stub option selected in the advanced tab.
Note that the synthetic full backup will be considered as the third backup cycle and it will render the stubs in the first cycle prunable. |
7 | Running the synthetic full backup will start a new backup cycle. Due to the change in storage policy retention all the previous backup have expired. |
8 | Run a data aging job. All jobs from the
first backup cycle will be pruned. Note that space on secondary storage has been freed up as all the unwanted stubs and their corresponding data have been pruned. |
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.
The platform specific files that are automatically filtered from archiving are:
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 following registry keys can be used to set additional filters for an archive operation:
sSTUB_PRUNE_PATTERNS |
Use this registry key to specify additional filters. Ex: sSTUB_PRUNE_PATTERNS *.so *.so.* *.a *.lib *.sh *.ksh *.csh /usr/** /bin/** /lib/** /etc/** /var/** |
sSTUB_PRUNE_EXCEPTIONS |
Use this registry key to set any exceptions to the filter list defined
in sSTUB_PRUNE_PATTERNS. Ex: sSTUB_PRUNE_EXCEPTIONS /var/log/abcd/** |
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:
|
![]() |
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. |