EFTA00764717
EFTA00764718 DataSet-9
EFTA00764720

EFTA00764718.pdf

DataSet-9 2 pages 377 words document
V15
Open PDF directly ↗ View extracted text
👁 1 💬 0
📄 Extracted Text (377 words)
From: "William Murphy" To: "Jeffrey Epstein" <[email protected]> Subject: iTunes Library Date: Tue, 09 Feb 2010 15:06:50 +0000 Attachments: Primary-New_York.pdf; Seconday-Low_Bandwidth_.pdf Good Morning Jeffrey, I spoke to an Apple sales representative and a systems engineer there last week to discuss possible solutions for a single library that spans multiple locations. The goal, as requested, was to have a single repository for media (movies, podcasts, music, etc). The library name would be the same at each location so you would be able to open iTunes and find the same media on the local Apple xServer. This system was designed to have a central site that pushes changes out to node sites. Should node sites have new content added to their library, an update would then be pushed back to the central site where changes would be pushed out to any other node sites missing the new content. As such, the central site was designed with redundant entry-level Apple xServers. They will maintain a heartbeat with one another to ensure that there is always a server available to handle requests. The node sites will have a single xServer that connects to a RAID array where the media will be physically stored. The Promise RAID arrays are devices that hold 16 drives; 14 of which will store data. This provides redundancy for the data so that should a single drive fail, the whole system is not lost. The system is connected via fiber-channel providing the fastest possible access means and ensuring there will be no performance bottlenecks with the hardware. The central site will have a new tape solution connected that can grow as required with additional drive space. I requested 2 RAID arrays initially for each location expecting one to be for music and one for video. The reason for this is that the Promise RAID cages are presented to the OS as a single volume. This means that in the future, additional drive cages would have to appear as /Library2, ILibrary3, etc. A better naming convention would be to have /AudioLibl, NideoLibl. Once these are filled, we could add additional drive cages as /AudioLib2 etc. Please let me know when you have some time so we can discuss. Thanks, WM EFTA00764718 William Murphy Systems Administrator — HBRK Associates EFTA00764719
ℹ️ Document Details
SHA-256
cf82b0ed9de11ce0e2f64df880f14d88cabcde3251eaa99446d71aa6f462571d
Bates Number
EFTA00764718
Dataset
DataSet-9
Document Type
document
Pages
2

Comments 0

Loading comments…
Link copied!