The DAM Forum
Welcome, Guest. Please login or register.
June 19, 2013, 03:24:08 AM

Login with username, password and session length
Search:     Advanced search
Jan 9, 2012
John Beardsworth's new Lightroom site
Lightroom Solutions
27968 Posts in 5116 Topics by 2914 Members
Latest Member: imthedamstar
* Home Help Search Login Register
+  The DAM Forum
|-+  DAM Stuff
| |-+  Hardware Discussions
| | |-+  HD set-up advice
« previous next »
Pages: [1] Print
Author Topic: HD set-up advice  (Read 1339 times)
Mark Mendelsohn
Newbie
*
Posts: 4


View Profile WWW
« on: August 01, 2006, 01:22:01 PM »

I'm about to get started with a new configuration of drives,  in an effort to take advantage of Peter's DAM teachings, and I'd like some advice, before I run amuck moving my files.  Then, I'll run amuck.

Here is my set-up:

Windows P.C. (You've heard of those, right?) with 80 GB internal HD.  About 25 GB is available.
2 - SATA WD 320 GB HDs in a 4-bay enclosure (2 empty bays for future expansion)
80 GB LaCie external HD - USB connected
200 GB Maxtor II external HD - Firewire 400 connected

My thinking:

One 320 GB SATA drive for Archive Files
The other 320 GB SATA drive for Archive Files and Working Files Backup
Internal P.C. HD for OS, apps and non-image data
Maxtor External HD for OS and Drive C backups - ideally stored offline
LaCie 80 GB External for Working Files and PS Scratch Disk

Would you do this differently?  I particularly wonder whether I'm putting my working files and scratch disk in the right place.  Thanks in advance for time and attention, and many thanks to Peter and others, from whom I've learned so much on the DAM Forum.

BTW, I would like to give cudos to MacGurus.  I just purchased a 4-Bay SATA box and PCI card from them to add to my P.C.  They were amazing in their knowledge and helpfulness.  I'm not that sophisticated,  and they walked me through the purchase, assembly and the actual set up.  They made it a breeze.

Mark


Logged

Mark
Marc Rochkind
Hero Member
*****
Posts: 1136


View Profile WWW
« Reply #1 on: August 01, 2006, 05:55:14 PM »

Mark--

What's your backup plan for archive and working files?

With the backup drive in the same enclosure as the primary drive, both are equally at risk for fire, theft, flood, surge, and certain hardware failures. I think you're protected only against the risks of user and software (non-OS) error.

You need as much separation as possible. Distinct power supplies, controllers, and cabinets, at the least. Also, you need a plan for regular offsite backup to protect against most risks.

My suggestion is to start by listing the risks you need to protect against, rank them according to their likelihood (hard to guess) and your willingness to accept the damage, and then design the scheme to bring the risks into an acceptable range. Example: You decide the risk of fire is low, and are willing to risk a week's worth of work in that event, but no originals. Or, you might decide the risk of fire is higher and/or you're not willing to risk a week's worth of work. Every situation is different, but the solution must match the problem.

For digital photographers, some ideal forms of backup, such as online, aren't practical, so the job is much tougher for us.

--Marc
Logged

danaltick
Hero Member
*****
Posts: 1616


View Profile WWW
« Reply #2 on: August 01, 2006, 06:11:04 PM »

Mark,

Looks like you have a pretty nice setup.  I have only a few recommendations.  Always place priority on your faster internal or external SATA drives.  They are going to outperform your USB and Firewire by a factor of at least 2 to 3 times.  Keep your primary workflow on those drives.  Therefore, I would keep my working files folders on either one of the SATA drives or (even better) on a second partitoin on the 80GB internal drive (the D partiton).  If your shoots are currenlty small enough to use the 25GB left over space, that's where I would put the working files folders.  If that's on a separate partition, you don't have to back it up along with the O/S.  Just image the C partition.  Backup those working files to the external 80GB USB drive.

I would also place my PS scratch disk on an internal drive as well for performance reasons; preferably the D partition if there is room.  I use Windows and have found that the C partition never even comes close to using 40GB.  All that I keep on it are my apps and O/S.  If I install any games, which can be large, they will go on another partition.  I currently have an 80GB drive like you.  I have it split into two partitions, C and D at 40GB's each.  I use the D partition for my working files folders.  I am going to be building a new PC soon and it will have probably a 120GB O/S drive.  I will still use only 40GB for the O/S partition and the remaining 80GB will be used for my working files.  That keeps my working files folders off my archive disks.  That way if I lose one of those disks, I don't also lose my working files, and those disks can be devoted to my archive.  If you can't accomodate this you will just have to compromise and put your working files on one of the archive disks, but I would use the USB and firewire drives only for backups.

I'm also assuming you are able to backup those SATA drives to other external drives.  If not, I would use one internally as the primary archive and the other in the external enclosure as the offline backup.  I would then place both my derivative and Raw buckets on the primary drive together and back them up to the external SATA.

Marc, looks like we posted at the same time ;-).

Dan
« Last Edit: August 01, 2006, 06:21:20 PM by danaltick » Logged

WindowsXP, ImageIngester Pro, RapidFixer, IVMP 3, ACR4, Photoshop CS4, Controlled Keyword Catalog, Canon EOS50D
Mark Mendelsohn
Newbie
*
Posts: 4


View Profile WWW
« Reply #3 on: August 02, 2006, 06:31:32 AM »

Marc and Dan,

Thank you, both.  I'll revise my plan to incorporate your advice.

I'm glad I asked.

Mark
Logged

Mark
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!