StorageEdge 3.4 SP1 brings many new features which optimize and manage storage in an efficient way. Here is a brief overview of what's new in StorageEdge 3.4 SP1:
Now in StorageEdge 3.4 SP1 you can link all newly uploaded BLOBs with linker profile using dual mode linker. Dual mode linker links all the lately uploaded BLObs with the configured linker profile.
Now in StorageEdge 3.4 SP1 you can keep older versions of the linked documents on a linker device. Moreover, sub folders can also be created for versions of each files.
Now in StorageEdge 3.4 SP1 you can revert content on the basis of some filters. While scheduling a Revert Job you can also add any filtering policy and if any filtering policy is defined then BLOBs will be reverted on the basis of specified filtering policy.
This feature provides you the option to monitor SharePoint Timer Jobs specific to StorageEdge. Now you can pause, resume or delete a job from this page. Furthermore, you can run a scheduled job at any time using "Run Now" option.
Now you can see all the executed jobs and their details through job history. All jobs either successful or failed are listed on this page.
Its a GUI tool used to revert content from externalizer to database. It is helpful in a situation where revert job fails to run from externalizer profile.
With this feature, users can manage their legacy file shares through SharePoint document libraries. Linker links all documents in file shares with SharePoint in such a way that documents remain on the file system and only their references are added to SharePoint content database.
For compliance, StorageEdge can now store copies of BLOBs and their metadata outside the database. Users can specify the retention policies as to how long to keep the archived BLOBs and when to delete.
To reduce the latency while writing BLOBs to cloud storages, users can opt to asynchronously upload files. This will write BLOBs to staging devices from where they will be uploaded asynchronously to the cloud storages.
If SharePoint content database is mirrored, StorageEge automatically starts using the failover database server if primary server is down or inaccessible. Similarly, StorageEdge BLOB store database can also be configured for SQL mirroring.
Since DFS shares can be addressed the same as any other file shares, with StorageEdge users need only to point their BLOB store location at the DFS share where they want their SharePoint BLOBs to be located.
Each tier in an Externalizer and Archiver profile is associated with a storage pool which can have one or more storage devices. More devices can added to a storage pool at any time.
Following new filtering policies are added.
Consistency check job makes sure that the BLOB references on content database, StorageEdge configuration database and external store are consistent with each other. This inconsistency can be produced as a result of restoring SharePoint site and databases from backups.
Along with aging based retention policy, there is a new usage based version policy which can be used to move documents to any other tier if the number of times document is accessed between two consecutive BLOB Transfer jobs is greater or less than certain number.
Users can now control which versions of the documents should be kept on which tier.
Externalized BLOBs can be configured to remain on external store at least n numbers of days after the corresponding documents are deleted from SharePoint.
If filtering policies of externalizer profiles are changed after offloading BLOBs, users can opt to run this job to make sure that these BLOBs meet the filtering criteria of their tiers.
Users can now write their own storage providers and plug them to offload the BLOBs to these providers.
BLOB details page now shows the details of all versions of a document.
Administrators can migrate or revert individual documents from BLOB details page.