Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

How to copy and back up?

G

glik

Banned
Joined
Oct 13, 2007
Messages
54
Reaction score
0
Points
0
Hello, we are shooting a feature with the red one.
what is the best way to copy the rushes from red hard drive to another hard disk? what should I take care of? is it a simple copy paste action? does fire wire400 is faster than usb? should I use back up program? why?
Thanks,
Glik.
 
Copy and paste is not ideal. It lacks any sort of oversight and i highly prone to human error and potentially machine error too.

There is an application out that is designed to automate the process somewhat. I can't remember what it is just now. Otherwise many people use backup or file synchronisation tools. Even Microsoft's own SyncTool is an improvement. Otherwise, a the very least a command line (XCOPY in Windows, or cp in OS X) tool is probably a better choice.
 
For what it's worth, I've been using Shotput Pro from imagine products, and it's worked out pretty well. Go to www.imagineproducts.com and check it out...the same program can also download P2 and Sony sxs cards. I think the app is less than $ 90 USD. FW400 or 800 seem to be running faster than USB 2.0.

Hope this helps, and best,

J
 
One point is to concern is to use multiple ports when you are copying.

Firewire 800 is fast but if you mix with 400 then the speed is going to be 400 worth.
Also, when you connect two 800s then that will use up the whole bandwidth.

If you are on Mac book Pro, the fastest way is to use the internal FW800 and eSATA or FW800 on the Express34 slot.

These things will be improved when USB3.0 or Firewire 3G compatible CPUs and devices come out.
 
One of the problems many users have found with copies via the finder is that if there is an error, finder will just stop - and it may not alert the user its done so. For example if there is suddenly no more disk space, it will just stop and not alert the user.

R3D Data Manager was designed to copy everything, check its all there and verify that the copies match the original, bit for bit. And it provides a way to ensure that the copies are valid in the future.
 
The same issue with copies just stopping applies to copies made in the Windows file explorer too. While it will usually alert you that it's failed, it's very difficult to pick up from where it left off. You have to do the whole thing again.
 
hey guys
I've seen R3D Data Manager and it looks good for copying redmedias on set...

But does anyone know a good app for copying a hole HDD to multiple destinations incl LTO3a? that also does a checksum before giving a report.

kind of the same stuff that R3D Data Manager does. But instead of copying just a CF-card/Red-drive over to HDD's. It should copy the HDD from Set onto a raid / LTO for archiving.

/carl
 
I have an early prototype of a program I had previously written, and now rewritten, called Safecopy, for windows.

It will copy an entire drive to another. All non-system, non-hidden files are copied to a folder on the destination drive, named source_volume_label.bak.

The copy is verified on the fly (ie, it reads back what its just written and verifies it against data its just read, before transfering next chunk of data)

All successful copies are logged into a text file in the root of source_volume_label.bak, as are skipped filenames and any file copy errors/verification failures.

This verified copy method is quicker than a cut and paste also.

At the moment i think its working, but would like anybody interested in helping me test it out to PM me, and I'll send a copy.

Testing should be performed whilst NOT on a shoot since the program is alpha release.

Also, please resist asking for a copy if you're not likely to give some feedback, feedback is payment, but also essential for finding any bugs with such a potentially critical application.

It will be freeware once tested, and will copy to multiple drives. thanks
 
the ".bak"... is that kind of like an image-file of the coped drive?
Meaning after its done, I can't brows the new folder to see whats in it...

/carl
 
C_Skaff said:
hey guys
I've seen R3D Data Manager and it looks good for copying redmedias on set...

But does anyone know a good app for copying a hole HDD to multiple destinations incl LTO3a? that also does a checksum before giving a report.

kind of the same stuff that R3D Data Manager does. But instead of copying just a CF-card/Red-drive over to HDD's. It should copy the HDD from Set onto a raid / LTO for archiving.

/carl
Click to expand...

Guys-

This has got to be one of the BIGGEST misconceptions about R3D Data Manager. It reads from ANY MEDIA. A Red Raid, a red CF card, or your hard drive, or even a network drive - it DOESNT MATTER.

As long as your media appears as a mounted drive, it can be the SOURCE or DESTINATION for any copy. Infact, if you wanted to and were so inclined you could copy FROM a HDD to a RED CF CARD!

R3D Data Manager provides a END-TO-END copy and verification process, and you should use R3D Data Manager EACH and EVERY time you copy R3D files, to ensure they are complete and precise.
 
use StorageDNA to move, sychronize and/or archive RED data

use StorageDNA to move, sychronize and/or archive RED data

You might want to use StorageDNA software to manage your data.
Basically with a StorageDNA enabled workflow you could have automated local LAN or remote WAN synchronizations of your footage. If you want to try it out you can get a trial app from the company web site. http://www.storagedna.com Please be sure to mention that you are a RED user in the request form.
 
Anyone have a typical data move time from RED drive to backup drive(s), FW800 usingR3D Data Manager? Maybe the time it takes to move 100 gigs.
thanks
 
The time it takes to transfer is highly defendant on your system - the speed of the drives, how they are hooked up and the type of checksums used in addition to other factors.

For instance, having 2 or 3 drives on the same bus will slow down transfer times by 30% to 70%. So I would recommend not using firewire 800 to write to if it is on the same bus.

In addition, copying to multiple destinations at once will slow it down when copying from the Red Raid - as the seek time trying to find the data for multiple sets of copies will drive your total transfer time down. Finder suffers from this also.

One last point - you have to consider that the only way to verify your data is by reading it 3 times - once to create the checksums, once to copy the data, and once to verify the copied files. Finder and Explorer dont to that, so it seems to be 'faster', at the expense of 'safer'
 
Just use rsync as root. Is already on all macs. The down side is that it's a command line tool, so if you'r not used to that is abit ackward.

I think RED is saying you should use the DiskTool and make a image of all drived and medias.
 
I have not personally used R3D Data Manager in a while - so, someone correct me if this my comments here are outdated and my issue/concern has already been addressed.

My biggest issue with R3D Data Manager is that IT WRITES (CHECKSUMS) onto your digital negative.

I don't want ANYTHING writing to my digital negative except the camera. Period. All copies should be clones of the volume as the camera created it.

I never understood why R3D Data Manager doesn't allow you to SET A DESTINATION FOLDER for the checksums - so you can write them on a volume which is not your camera media.

Did this feature already get implemented?
 
You must log in or register to reply here.
Back
Top