[Cytometry] archiving data in a flow core?

Cris Bare flowmail at verizon.net
Tue Feb 18 18:12:34 EST 2014

Different facilities with different usage loads can have vastly different
methods. When I started at Gladstone, each user (and there weren't a huge
number) was responsible for self-archiving on MO disks (having replaced the
Bernoullis). Other institution that didn't have robust central data shares
meant I burned a lot of CDs for users.

At Rockefeller, Paul Nurse instituted a strong IT directive. Working
closely with IT we established a series of scripted transfer apps to users
lab/personal data shares. On a nightly basis data and other relevant files
(sort reports, PDFs of layouts) were transferred by network using high
level permissions and low level commands.

Then in a rather brutal fashion the scripts would delete files from the
local drive and execute disk maintenance. I say brutal because there was no
recovery from the Recycle bin when using a script.

We posted warnings and personally informed all users before implementing
this system. After a few weeks they got the idea and most of them kept
additional backups.

Institutionally, Rockefeller used Iron Mountain for data backup. This
created a safe and redundant system.



On Sat, Feb 15, 2014 at 11:13 AM, Ian Dimmick
<ian.dimmick at newcastle.ac.uk>wrote:

> Hello Ruth, The policies for archiving data are generated , in the main,
> by the grant funding bodies, and must be complied to .
> We have to ensure that all of our data for certain grants is archived for
> at least 10 years, some grants for longer.
> If however you are not in receipt of grant specific archive  instruction
> then we use the following procedure (for us this is suffice for all
> eventualities.
> 1-We use the FCS expert function within Diva to immediately export data
> once it has been generated onto University data storage , this , because of
> the architecture of Diva , is also stored on the local computer .
> 2-At the end of each month  all experiments and the database for the month
> are exported onto both the local D drive and onto an archival drive(backed
> up storage) specific for the instrument/moth/year , this is done for all of
> our 10 flow cytometrs
> 3-all data is deleted from the Diva database, a defragmentation step takes
> place , hence each month ,for each instrument we start with a clean
> database, but have the ability to recall any experiments at any time
> Hope this heps
> Ian
> -----Original Message-----
> From: cytometry-bounces at lists.purdue.edu [mailto:
> cytometry-bounces at lists.purdue.edu] On Behalf Of Ruth Nissly
> Sent: 14 February 2014 19:17
> To: cytometry at lists.purdue.edu
> Subject: [Cytometry] archiving data in a flow core?
> Dear flow-ers,
> If you are in a flow cytometry core facility, I have a question: What are
> the policies held by your core regarding data storage & archiving?
> Specifically:
> -How long are users allowed to leave data on the acquisition computer?
> -How are data files older than this time-period removed from the
> acquisition computer?
> -Are old files stored as backups by the core? If so, for how long are the
> backups stored?
> We're getting to the point where it's taking a lot of time and money to
> archive data that very few people actually ever request, so your
> advice/experience would be helpful in deciding how to move forward. For
> reference, we have files collected using CXP, Diva, Spigot, and Summit --
> and we will soon also be getting imaging flow cytometry files.
> Thank you,
> Ruth Nissly
> research technologist
> Microscopy & Cytometry Facility
> The Huck Institutes of the Life Sciences Pennsylvania State University
> W-124A Millennium Science Complex
> University Park, PA 16802
> 1-814-863-2762
> rah38 at psu.edu
> _______________________________________________
> Cytometry mailing list
> Cytometry at lists.purdue.edu
> https://lists.purdue.edu/mailman/listinfo/cytometry
> Search the list archive at  http://tinyurl.com/cytometry

More information about the Cytometry mailing list