[Pasig-discuss] Write-blocking a RAID

[Chris Wood]

Good idea Jacob. Other ideas are:

1) mount file system RO.
2) export RAID volumes RO - assuming the array has this function
3) backup all data to a non-rewritable tape like Oracle Storage-tek Vol-safe tape media,
4) copy all data into a file system with WORM capability like Oracle SAM-QFS

Pls feel free to email or call.

Chris Wood
(408) 218 7313
Chris.wood at oracle.com
Sent from my iPhone

On Nov 1, 2012, at 12:55 PM, Jacob Farmer <jfarmer at cambridgecomputer.com> wrote:

> Joe, what operating system and file system is the server running? 
>  
> Also the email you forwarded (below) implies that the system might be broken in some way. Is it up and running and you just want to preserve it?  If so, I have software that can capture the file system metadata and preserve that along with a hash of each file.  Then you could store the files themselves in any kind of storage device. 
>  
> -> Jacob
>  
>  
> Jacob Farmer  |  Chief Technology Officer  |  Cambridge Computer  |  "Artists In Data Storage"
> Phone 781-250-3210  |  jfarmer at CambridgeComputer.com  |  www.CambridgeComputer.com
>  
>  
>  
> From: pasig-discuss-bounces at asis.org [mailto:pasig-discuss-bounces at asis.org] On Behalf Of Joseph Pawletko
> Sent: Thursday, November 01, 2012 2:55 PM
> To: pasig-discuss at mail.asis.org; digital-curation at googlegroups.com
> Subject: [Pasig-discuss] Write-blocking a RAID
>  
> Hello, All.
>  
> I've been asked by some of our archivists to preserve the contents of a RAID (and a server)
> and I'm looking for write-blocking strategies so that the file Modify-Access-Change data are not
> modified.
>  
> I discussed this problem with Mark Matienzo, who gave me permission to forward the email below
> in case others are trying to solve the same problem.
>  
> Has anyone used a strategy different from those outlined by Mark?
>  
> Thank you for your time.
>  
> Best-
> Joe
>  
> -- 
> Joe Pawletko
> Digital Library Technology Services
> Bobst Library
> New York University
>  
> ---------- Forwarded message ----------
> From: Mark A. Matienzo <mark.matienzo at nyu.edu>
> Date: Tue, Oct 23, 2012 at 12:48 PM
> Subject: RAID acquisition
> To: Joe Pawletko <jgp at nyu.edu>
> 
> 
> My understanding is that there seem to be two camps: 
>  
> 1) Acquire the contents of the array over a network, which requires the system to be live. This option is obviously less ideal because the contents of the system may change (logs, etc.), but doesn't require you to know as much about what RAID level the array is running. 
>  
> 2) Acquire each drive individually, removing them from the array. This obviously requires the system to be dead, but may add considerably additional work since you need to reassemble the array. This may be preferable if you know less about the system. There are a few different applications that can help with this: RAID Reconstructor <http://www.runtime.org/raid.htm>; X-Ways Forensics; EnCase. The specific software will depend on whether it's a software or hardware array. 
>  
> I don't really know what's preferable in this case - I think it largely depends on what you know about the server.
>  
> Mark
>  
> ----
> To subscribe, unsubscribe, or modify your subscription, please visit 
> http://mail.asis.org/mailman/listinfo/pasig-discuss
> _______
> Save the Date - PASIG Dublin, October 17-19, 2012
> _______________________________________________
> Pasig-discuss mailing list
> Pasig-discuss at mail.asis.org
> http://mail.asis.org/mailman/listinfo/pasig-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.asis.org/pipermail/pasig-discuss/attachments/20121101/4adc15d2/attachment-0001.html