Data Transfer and Storage using the RCR's Server
The School of Medicine has a heterogeneous environment and it is increasingly
taxing to figure out how to get the most out of it all. This page aims to help
with one of these problems: moving data between different platforms,
specifically onto and off of the RCR's UNIX server.
Using the RCR's UNIX server as a Fileserver for your desktop
A fileserver is a networked computer that runs software to permit files to be
stored on the server's local disks and made available over the network to
desktops that can use these files just like the files stored locally to that
desktop. If things work properly (yes, they nearly always do) the user on the
desktop machine can't easily tell whether a file s/he is working on is stored
locally or on a remote computer's disk on the other side of the campus (or the
world, in some cases).
The RCR's UNIX server, mcrcr0, can be used as a fileserver for either your
Macintosh or your PC desktop. This can be a big advantage for you: mcrcr0 can
be used for backing up critical files that will themselves be backed up to tape
overnight; mcrcr0 can be used as a staging area for files you need to move
between computers; with some minor limitations you can use files moved from
your desktop for analysis on the RCR and then access the results directly from
your desktop again.
CAP provides AppleShare file services to Mac users that can access
the RCR via EtherTalk (essentially, inside MSB only at this point). This
allows you to store Mac files, intact, on mcrcr0 and access them as if they
were on an additional disk drive on your desktop. The instructions on how to set up CAP are on this
link
SAMBA provides file services to PC users. This
allows you to store PC files, intact, on mcrcr0 and access them as if they
were on an additional disk drive on your desktop. The instructions on how to set up SAMBA are on this
link
The Limitations of file servers are obvious: If the server is off or
the network is down, you don't get access to your files. Network data transfer
speeds can't match that of a local hard drive. Generally, the space
available on the server will have a hard time matching that of the disk on your
desktop: I have a 10Gb disk on my desktop and the RCR server user space limit
is significantly less than that, so I can't just drop everything onto
mcrcr0.
The Benefits are equally clear. For all users, critical files can be
distributed so that data loss is much less likely (files on mcrcr0 are backed
up nightly). The fileserver function can be used to access some files in
apparently "native" form on a Mac, a PC and on the UNIX box, symultaneously: a
boon to the sophisticated user.
Shuttling files between Machines
One of the problems people have is moving files between machines. "Sneaker
net" is a favorite: you copy the file to a diskette or Zip disk and hand-carry
it where you want to go. This works fine, for small files that fit on disks
and do not need to travel faster than walking pace. Huge files, such as images
and complex databases won't work like this: you need to use the network.
The Direct Method
The most straight forward method to move a file from one machine to another, is to
copy it directly. For this to work, one of the machines needs to offer file
service, or at least an FTP server. In fact there are several packages that
allow you to turn your desktop into an FTP server that will accept incomming
files. Many of these are not particularly secure, and often they are not all
that reliable. RCR staff can help if this is a method you want to pursue.
Using the RCR as a staging area: via file service.
For the right kind of files, and image files are ideal in most cases, files can
be moved between, say, an image digitizer and your desktop using the file
service facilities, as follows:
- Mount mcrcr0 as a file server on the digitizer.
- Drag and drop or otherwise copy the images from the digitizer disk to mcrcr0.
- Dismount mcrcr0 from the digitizer and make sure access to your space on mcrcr0 is secured.
- Go back to your office.
- Mount mcrcr0 as a fileserver on your desktop
- Drag and drop or otherwise copy the images from mcrcr0's disk to your desktop.
- Delete the files from mcrcr0 if you need to.
- Dismount mcrcr0 and make sure access to your space on mcrcr0 is secured.
- Be happy: you're done!
Using the RCR as a staging area: via FTP.
The RCR's server runs a FTP server. Using this, you can log into mcrcr0 and
drop files off in your area, and then log in from another location to retrieve
them: this is the method you'd use from an image digitizer to get images you'd
scanned from the digitizer to your desktop using mcrcr0 as an intermediary
host. The FTP protocol is fast, efficient and reliable, but is intended for
the transfer of data only. Images are ideal for transfer, as are "packaged"
data and programs where any additional context, which is part of the usual
Macintosh file, is encoded into the package. On the Mac side, "Fetch" is the
usual best choice. On PCs there are several good choices. Basically, both the
PC and Mac products allow you to "Drag and Drop" files (such as images) onto
the FTP server, or from the server to your desktop. For the particular case
when images are being moved, the FTP server solution is easiest to implement
since it trivial to set up and works in nearly every circumstance.
|
