Archivierung von Musik: PROBLEM mit neuen HDDs

stehe kurz vor einer kaufentscheidung, je mehr man liest desto unsicherer wird man jedoch.

ziel:
# speicherung meiner musik (flac und mp3) + bilder + ein paar filme und andere daten auf externer hdd mit usb

dabei soll zum beispiel auch mal alles an den blu-ray player angeschlossen werden oder an ein internetradio.

natürlich kommt es mir speziell beim musikarchiv auch auf eine gewisse sicherheit an.

ursprünglich wollte ich daher das hier kaufen: http://www.amazon.de...&colid=2SXR8T1RGSYI2
hätte den vorteil, dass ich einfach usb an den blu-ray player hängen könnte und den pc an firewire, erspart nerviges umstecken oder umschalter.
ich würde dann alles spiegeln lassen. nun lese ich aber immer mal wieder ein raid sorgt nicht für datensicherheit sondern nur für ausfallsicherheit. ja was denn nun? wenn eine hdd im raid kaputt geht und ich die daten auf der anderen gespiegelt vorliegen habe dann ist das für mein verständnis relativ sicher.

wegen meiner verunsicherung habe ich nun an folgende lösung gedacht:
2 mal diese hier kaufen http://www.amazon.de...75153&pf_rd_i=301128
eine dient quasi als hauptspeicher und die andere wird regelmäßig angeschlossen und dann wird zum beispiel mit personal backup alles auf der zweiten gesichert. falls dann mal eine kaputt geht ist alles noch auf der anderen vorhanden.
diese lösung wäre in meinen augen nicht ganz so komfortabel, aber erheblich günstiger vom preis her.

was wäre denn nun im eigentlichen sinne empfehlenswert bei den gegebenen anforderungen???

Wenn sich jemand näher für den Indexing Service interessieren sollte :



Created for and first delivered with Microsoft Internet Information Services (IIS), Indexing Service is a feature originally designed to facilitate fast and flexible searches for information stored on Web sites. Because its query technology can be applied to ordinary disk storage as well as to Web sites, Indexing Service has become a core component of Windows (beginning with Windows 2000) and is integrated with Search Companion.Indexing Service extends the power of Search Companion in several ways. First, it can speed up searching dramatically. How much performance gain you’ll see depends on many circum-stances. But in tests for this book, we often found that some content searches ran on the order of a hundred times faster with Indexing Service than without it.

Second, Indexing Service’s query language lets you find files on the basis of many different properties in addition to the size, date, and file type. With Indexing Service enabled, Search Companion can locate a file on the basis of word count, most recent editor, most recent printing time, and many other attributes.

Indexing Service obeys the rules of NTFS file security. If a catalog (the collection of files used by Indexing Service to record the contents and properties of your files) resides on a local NTFS disk, the access privileges of the user executing a search determine the results of that search. The service will not return the names of files for which the user does not have at least Read access permission. If the catalog is stored on a network drive accessed by means of a Universal Naming Convention (UNC) path, the user might see the names of files for which he or she lacks Read permission but will not be able to open any such files.By default, Indexing Service creates its catalogs in folders to which only the System account has access. This precaution prevents accidental deletion. More important, it helps maintain security. As long as the default access permissions for the catalog folder are not changed by an administrator, you can be assured that the catalog files themselves are not subject to unau-thorized inspection.Indexing Service never indexes encrypted documents. If a file is encrypted after being indexed, the service removes it from the catalog.Limitations of Indexing ServiceDoes using Indexing Service have drawbacks? Not many. But here are some things you should know:

●Indexing Service requires disk space. Because Indexing Service catalogs your disks in the background, during periods when your computer is idle, you don’t pay a perfor-mance penalty for running the service. You do, however, sacrifice some disk space. Microsoft estimates that the catalog will consume from 15 to 30 percent of the size of the indexed files. Prudence suggests assuming the higher figure is more accurate.

●Indexing Service catalogs the content of only certain kinds of files. By default, Indexing Service catalogs the content of the following document types:
■HTML files (their text)
■Text files
■Documents created by Microsoft Office (version 95 and later)
■Any other document type for which a suitable filter is installedA filter tells Indexing Service how to separate meaningful text from file headers, for-matting information, and all other nontextual elements. Microsoft provides filters for HTML, text, Office, and mail and news documents. Third parties might provide filters for their own documents. If you use a non-Microsoft office suite, you might want to check with that product’s vendor to see whether an Indexing Service filter is available.With an optional setting available via Indexing Service MMC console, you can set the service to index files with unknown extensions. (For details, see “Indexing Files with Unknown Extensions,” page 657.) If you index files with unknown extensions, the ser-vice tries to extract meaningful content from file types other than the ones it catalogs by default.
●Indexing Service ignores “noise” words. The list of words ignored by Indexing Ser-vice appears in the file %SystemRoot%\System32\Noise.xxx, where xxx is a three-letter abbreviation for the language you use. The file is plain text, and you can edit it with Notepad. The noise filter for English, Noise.eng, includes common prepositions and conjunctions, articles, relative pronouns, various forms of the verb to be and other common verbs, individual numerals, individual letters, and a handful of other fre-quently occurring words.If you include a noise word in a search string, the service treats that word as a place-holder. For example, in the search string “age before beauty,” before is a noise word. Indexing Service will treat this string as equivalent to “age after beauty,” “age without beauty,” and so on.
●Indexing Service ignores case. If Indexing Service is not running, Search Companion can perform case-sensitive content searches. With Indexing Service running, it can’t.
●Indexed searching is not always available, even if you have enabled Indexing Service. If the service hasn’t finished building its initial catalog, or if it’s busy updat-ing the catalog, Search Companion simply dispenses with it, performing an ordinary (unindexed) search.