Talk:Hierarchical storage management

From Wikipedia, the free encyclopedia

Request to add a reference to Moonwalk which is a HSM for Windows, NetWare, Linux. It's unique in that it has no databases or middleware with built-in Disaster Recovery. http://www.moonwalkinc.com/. There are plenty of references to it via byteandswitch such as http://www.byteandswitch.com/document.asp?doc_id=118998&page_number=8

Rudnuts 08:47, 5 July 2007 (UTC)

[edit] Merge Tiered storage into Hierarchical storage management

HSM is a well-known term (together with ILM) and HSM article sufficiently describes technical aspects of a problem. Sure, tiered storage can be defined as a superset of HSM and several other minor cases, but I think it is pointless. --Kubanczyk 22:30, 6 September 2007 (UTC)

Tiered Storage can be present for other reasons than HSM. Consider the ITIL Service Management topic of Service Level Agreements and Operational Level Agreements. Tiers can be presented as an option for storage without HSM tools moving data into or out of it, based on SLA and/or attributes such as price/performance. Thus, you could have a high performing, highly available tier, and a lower priced economy tier that may have different performance, availability and/or price attributes. A data center could offer both tiers, and an application could wholly utilize one or the other with no need for an HSM solution to migrate data. While the use of tiers can be significantly enhanced by HSM, they should remain separate topics. Architect Ed 21:24, 8 October 2007 (UTC)

Disagree: Although I grant that Tiered Storage is very closely related to HSM, I don not think that merging both topics would be a good idea. Tiered storage gains its value from HSM, but HSM can be looked upon without much thought about hardware. Thus, I think this should be kept separate. —Preceding unsigned comment added by 195.212.29.163 (talk) 12:32, 12 November 2007 (UTC)

Agree: also can add the fact that a HSM is storage policies executed to automate the movement of files within Tiered Storage Rudnuts (talk) 15:36, 20 December 2007 (UTC)

Yes, the tiered storage and HSM articles should be merged. The two are too conceptually close to be considered different. Public Menace (talk) 02:55, 26 December 2007 (UTC)

Disagree: HSM (hierarchical storage management)is an applications and teired storage is a plan or concept. HSM applications are used to move binary large objects (BLOBs)for one tier type to another, usual from an online disk, to a nearline disk, tape or optical device. The HSM products are primarily used for data archive. While tiered storage is based on the needs of an application or content used by an application. Here you look at data access requirements, overall throughput, storage capacity, processing type, and access types. This can range from a highly transactional database to a long term offline archive. --PresArch 16:04, 18 February 2008 (UTC) —Preceding unsigned comment added by Carlwatts (talk • contribs)

Agree.. Tiered Storage is little more than a stub. I'd say break it off later if it grows into something big. --32.97.110.143 (talk) 18:29, 7 March 2008 (UTC)

Agree. TS is one way of doing HS, worthy of a paragraph in HS. Ray Van De Walker (talk) 01:06, 30 April 2008 (UTC)