Hi guys,
EV can uses SIS during save items to ECS. Many thanks
DELL notices inside its documentation that ECS doesn't SIS , see bellow, but EV uses SIS algorithm before saving data to ECS object storage ( I hope) . Therefore, advantage of SIS we can use
Single instancing
Unlike the Centera system, ECS does not single-instance duplicate objects that are stored on it. ECS uses
inline compression to reduce the storage consumed when storing objects
https://www.delltechnologies.com/asset/en-us/products/storage/industry-market/h15310-centera-ecs-tec...
So, ECS uses compression technology.
Do you have a experience with capacity planning of ECS ?
We have enable SIS on current NTFS partitions and we have original capacity 85TB ( EV report, see bellow) and our NTFS partitions have perhaps 30TB occupied.
Total size of archived items MB : 73321170
Total original size of items MB: 84890124
Can I assume that ECS store with API Streamer will take approximately the same capacity ? Is there capacity calculator for ECS with EV ? ( I have EV calculator ).
And second question. Do you have experience with any tools for move archive from NTFS to ECS ? We don't use Exchange mailbox or journal archives, but SMTP office365 archive, Sharepoint and File System archive ( there are not supported archives for Move archive task)
Many thanks ....
Petr
