![]() The production array hosts all my assets, projects, svn repository and files, while the backup array stores a mirror copy of the production array and of my different computers hard drives. I use a Sonnet Fusion D400 to store my drives which connects through eSATA to a dedicated controller in the server. ![]() The server uses two RAID 1 ifttt (mirrors), one for production and the other for backups. A VPN connection secures me in when I'm out, and svn over ssh gets my files in and out securely. ![]() The resources need to be available at all times as I don't always work in the office. The general idea is to have my project files and assets available at all times should I be in the office of not. My situation is not exceptional: I have a server in the office serving my files, svn repository and development websites to a Mac Pro in the office or a MacBook Pro out of the office. The main issues I had were related to running automatic unattended backup, off site rotation of a full copy of the backup, and overall reliability. ![]() I've sadly seen too many disks crash over the years to know that sh*t happens. As you may or may not know, I'm a paranoid sucker when it comes down to backup. I've recently fine tuned my overall backup strategy and finally found a balance between efficiency, security and ease of use that suits me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |