Alachisoft StorageEdge - Online Documentation

Adding a Storage Tier

 
To add a Storage Tier, follow the steps given below:
 
 
Adding a Storage Tier:
 
  • At the right side of the page, you will see "Add a Storage Tier" option, click on it. It will open a new page for storage tier settings.
 
 
  • On the next page, specify the name for the storage tier.
 
 
Storage Pool:
 
Select an already created Storage Pool from the drop down list. You can also create a new storage pool from here.
 
 
 
Compression:
 
Optionally enable Compression by checking the Enable checkbox.
 
 
Encryption:
 
Optionally select an Encryption Provider – AES 128, 3DES 128, 3DES 192, DES 64, RC2 128 or AES 256 for enabling encryption on a Storage Tier.
 
Note: If any of the Encryption providers is selected from the list, "Generate key" should be mandatory in order to proceed.
 
 
Delay Deletion:
 
Storage Tier can be configured to retain externalized BLOBs on external store for at least n numbers of days after deletion from SharePoint using this feature. To use this feature you need to enable the delay deletion and specify the number of days to keep the BLOBs after deletion.
 
 
Folder and File Names:
 
Here you can specify whether the BLOBs should be externalized in folders or not. It will help you to define the file name and the folder structure for your content. You are provided with the facility to keep the data in a same file structure as it was on your local disk. This facility is provided to users at tier level. Here you are given a choice to select file and folder structure, choices are:
 
  • "Do not create folders" option will save the data in a flat structure, no folder hierarchy is defined.
  • "Use SharePoint folder names" will save data in a same hierarchy as it was on SharePoint.
  • "Auto generate folders" option will auto generate the folder(s) with date time stamp. Here users need to specify the format for naming the folders which can be: hourly, daily, weekly, monthly or yearly.
  • "Use SharePoint file names" option can be used with any of the above 3 options. It will keep the file name same as it was on SharePoint.
 
 
 
Tier Filter Policies:
 
Filter Policies are provided to define the filtering criteria for the BLOBs that should be externalized. By default filtering is not enabled and all BLOBs will be externalized. Using "Add New Filter Policy" user can add required filters.
 
  • Size Filter: Here users are required to specify the "Size" in KBytes and the rule i.e. "Greater Than" or "Smaller Than" for the BLOBs that should be externalized.
  • Name Filter: Using this filter the BLOBs should be filtered on File name. Here you need to provide the name of the file which is to be included/excluded from externalization. It includes file type filtering and allows regular expression or multiple names/extensions (each on new line).
  • Author Filter: Author Filter allows you to either include or exclude the files of the selected authors to be externalized.
  • Last Modified By Filter: Last Modified By Filter allows you to either include or exclude the files of the selected authors who modify the files to be externalized.
  • Creation Date Filter: Select the "Creation Date" of the BLOBs that need to be include/exclude for externalization.
  • Last Modification Date Filter; Filter the BLOBs by "Last Modification Date" for externalization.
 
 
 
Specify BLOB Retention Policy:
 
Specify the retention policy for BLOBs to be kept in a tier. After the expiration of retention, the BLOBs will be moved to the next tier (if exist). Once data expires on a tier (i.e. according to defined policy, data will expire in 365 days) then it’ll be moved to the next tier and that tier doesn't accept the data then data will remain on the same tier. But if a tier is marked as a last tier then expired data will be deleted.
For example: The file stored on 1st tier will be moved to the 2nd tier on expiration of retention period. StorageEdge facilitates you with three BLOB Retention Policies on tier level, which are:
 
  • Aging:
  • Aging is use to specify the age of the BLOBs on a tier. After the specified age of the BLOB, it will move to the next tier.
  • Here user need to select the Aging retention policy from the drop down list, enable "Move BLOBs to next tier" and specify the number of days.
  • Aging is manifested from the creation date of the document.
  • Press Add button to save the policy for the tier.
 
 
       
  • Usage:
  • Usage based retention policy is used to move the content from the current tier to any other tier on its usage. Here the number of times the document is accessed between two consecutive BLOB Transfer jobs  will be considered. The BLOB will be moved to a cheaper storage device or to an expensive storage device depending on its usage. It will help to move the more frequently accessed documents from the cheaper storage to the high performance expensive storage tier.
  • If document usage is lesser, then it will be moved to the next (cheaper) tier whereas if document usage is greater then it will be moved to the previous (expensive) tier.
  • Here user need to select the Usage retention policy from the drop down list.
  • Enable the rule for the BLOB to move to the next and or previous tier. Specify the number of times the BLOB accessed and the number of days for the BLOBs.
  • Press Add button to save the policy for the tier.
 
       
  • Versioning:
  • Here user can specify the versions of the document which should be kept on this tier. Following options are provided to the users:
  • Keep the current version only: it will mark the tier to keep the latest version of BLOBs and move the older versions to next tier. If you create multiple tiers then you can apply this policy on only one tier.
  • Keep the current major and minor version only: it will mark the tier to keep all the latest major and its minor versions of BLOBs and move the older major, minor versions to the next tier.
  • keep current major and all its minor versions: it will mark the tier to only keep the latest major version and all its minor versions.
  • Keep last n number of major versions and their entire minor: it will keep n number of major versions and all their minor versions on the tier and move the remaining BLOBs to the next tier.
 
 
 
 
 
See Also

Copyright © 2012 Alachisoft. All rights reserved.