The hardware and software used to read and write modern media are out of use after an even shorter time, typically after five to fifteen years. The looser this interconnection is, the more likely is it that either hardware or software can be replaced without jeopardising the entire archive solution. Both are therefore dubious as long-term archive solutions. For these, an implementation following the IEEE Storage Reference Model is to be preferred. The object specification may be as common as a file path name in a hierarchical directory structure, or as exotic as a query of arbitrary complexity in a relational database.
Name services are completely optional in a storage system.
In contrast to that, ADSM imposes the file path structure of the client on the database of the server, thus rendering them dependent on each other. ADSM database performance ADSM database reliability performance in general more flexible configurations hierarchy of servers shared devices StorageTek support easier administration and tuning This is the list of the most frequently named requirements as found on the answers to the questionnaires sent out to the ALES members. There were 18 questionnaires returned when this list was prepared. Low performance may kill everything. Poor database resilience is considered a serious threat.