Understanding Archiving in DaVinci Resolve

Hi. Am hoping to finally get into working with DaVinci Resolve this weekend, but first need help better understanding something...

I want to make sure that I understand how ARCHIVING works in DaVinci Resolve.


Background:
Originally, I was going to create this elaborate filing system on my new MacBook Pro to hold all of my video interviews, when it occurred to me - this morning - that instead of building this elaborate filing system on my internal SSD, I really should be doing this on external SSD's.

As my new thinking goes...

Really all I need on my MacBook Pro's internal SSD is some generic directory to serve as a "workspace".

Then once I am done editing a DaVinci Resolve Project, I would ideally like to be able to bundle up all of my original media files, my project, timeline, etc. and store all of that on an external SSD.

Of course, to make all of this work, I need a way to take my ORIGINAL media files (i.e. video interviews, external audio, B-roll, music, etc.), PLUS the DaVinci Resolve Project files, and BUNDLE IT UP so that I can store everything in it's place on my external SSD's.


The hope would be that a DaVinci Resolve "archive" file would behave like this...
- End up with a SINGLE CONTAINER FILE.
- Which contains all ORIGINAL MEDIA files.
- Which contains all DaVinci Resolve PROJECT FILES (e.g. project metadata, bins, timelines, etc.)
- You can easily MOVE that "archive" file between drives and computers.
- And as long as you have a similar version of DaVinci Resolve, then you can open up said "archive" file and jump right back in to your DaVinci Resolve project where you left off!
- Because all of the COMPONENTS are in a single folder, there would be NO BROKEN MEDIA LINKS.

(To achieve this kind of PORTABILITY, this is why Java programmers store their projects as .JAR files, or why someone who needs to save an elaborate directory structure with business documents would choose a .ZIP file.)


Questions:
1.) When you create an "archive", is DaVinci Resolve creating a COPY of the original media files?


2.) When you create an "archive" in DaVinci Resolve, are the ORIGINAL MEDIA FILES left UNTOUCHED and in their ORIGINAL LOCATIONS (e.g. on an external SSD)?


3.) If I save my projects as a DaVinci Resolve "archive" (i.e. ".DRA"), will it have the PORTABILITY of say a .JAR or a .ZIP file, where I can move it from drive to drive, and computer to computer, and as long as I have a copy of DaVinci Resolve, I can open up that "archive" file, and pick up where I left off?


4.) Will using DaVinci Resolve "archive" files help me reach the above stated goals?


IF things work as I hope, then I can have a simple "01_STAGING" folder on my MacBook Pro, and then once a project is done - or at least a publishable video is created - then I can "archive" things, move them to a new home on an external SSD, and have the peace-of-mind knowing that I can easily find (a COPY of) all of the original media files, the DaVinci Resolve project, and the final videos all in one place, and I do NOT have to worry about "broken media links" - OR WORSE - broken projects!!

Hoping what I described above is attainable...

Looks to me like your understanding is accurate.
A .dra is a .drp plus the media the project needs.
The media is copied - the originals are untouched.

Joe,

Looks to me like your understanding is accurate.
A .dra is a .drp plus the media the project needs.
The media is copied - the originals are untouched.

Is the media inside the .DRA file accessible and even detachable?

My concern is this...

If I create a .DRA file after a project is done, I have duplicate media, and I *might* be inclined to delete the original media files since I have the .DRA file.

But conventional wisdom say, "Don't do it!!"

If you had to "extract" media files from a .DRA file, is that possible?

And what are the chances that a .DRA file become corrupt and so you lose your media files?

Depending on the answers to these questions, I have some other ideas...

To date I have not had any problems restoring an archived project from an external drive. May be try archiving a small project, moving the source files and .drp to a temp: directory and test that you can recover your project. If it fails to nothing is lost as it is not paid work. For safety the external backup/archive should be raid.

If you open a .dra folder and keep going you'll find a folder (or folders) with the media inside, which is independently accessible with the OS. This probably isn't recommended because they don't want you fooling with the archive contents or structure, but you asked.....

Another essentially equivalent way to make an archive is to do it manually.

Make folder and copy all your media into it. Then relink to that media. Finally, export a drp and save it to that folder. Voila.

And since you’ve done the relink you can tell if it was successful - as in the timelines play correctly - so that eliminates the one issue some people have where they make a dra with media that has insufficient timecode and end up with a mess when they try to restore it.

I really miss the simplicity of archiving that Vegas offered.

All the required files and project data could be stored under a single directory so that directory could be simply copied onto archival media and restored as/when required.

By comparison, Resolve is a little more complex... it'd be nice if we could have it automatically write project info into the project's directory so that things could be automatically archived as a simple file-copy during an overnight process.

One can certainly decide to store all their media under a single project directory.
At that point, isn't the only thing missing being exporting a drp to said directory after each session?

@John Paines,

If you open a .dra folder and keep going you'll find a folder (or folders) with the media inside, which is independently accessible with the OS. This probably isn't recommended because they don't want you fooling with the archive contents or structure, but you asked.....

Does that mean you trust .DRA archives enough that you would delete your original media, and just grab the archived original media from the archive if needed?

Or is that asking for trouble?

Joe,

Another essentially equivalent way to make an archive is to do it manually.

Make folder and copy all your media into it. Then relink to that media. Finally, export a drp and save it to that folder. Voila.

Yes, I was going to propose that approach also.

The important question is, however, if you take "Project123" which was pointing to media in "SomeFolder" and then you re-link "Project123" to media in "SomeOtherFolder", and then you make a .DRP backup and move it to "SomeOtherFolder" will the links work?

It depends on whether DaVinci Resolve uses RELATIVE or ABSOLUTE linking...

And since you’ve done the relink you can tell if it was successful - as in the timelines play correctly - so that eliminates the one issue some people have where they make a dra with media that has insufficient timecode and end up with a mess when they try to restore it.

This would be my preferred workflow...

- Download media from my iPhone onto my external SSD in the "Project1234" folder.
- File it in a reasonable location on the external SSD
- On my MacBook Pro, create a new "Project1234" in my "01_STAGING" folder.
- Link to the media on the external drive.
- Edit
- Render
- Make a .DRP backup of "Project1234"
- Save the .DRP file to the "Project1234" folder
- Have it so "Project1234" can be re-loaded in DaVinci Resolve and work.
- More importantly, if I need to RE-NAME the "Project1234" folder or MOVE it, it wouldn't break the links between the .DRP file and the media files all residing in the "Project1234" folder - whatever it's new name or location is. (In other words, the links would be RELATIVE.)

If that would work, then it would give me complete flexibility to re-organize my library and archives as things grow.

Not sure how DaVinci Resolve works with all of this.

I do agree that maybe .DRA files are scary because 1.) they embed your media in the file, and 2.) maybe the links would break and you would know until you RESTORED the .DRA.

(In IT, there is an old saying, "Backups don't mean squat. Successful recovery is all that matters.")

Joe,

One can certainly decide to store all their media under a single project directory.
At that point, isn't the only thing missing being exporting a drp to said directory after each session?

See above.

Depends on if linking is RELATIVE or ABSOLUTE.

I agree with @RCModelReviews that it would be nice to be able to create your own project directory, then dump all media inside that project directory (or sub-directories), and then have your DaVinci Resolve project be located in that project folder, and then everything is self-contained.

Not sure how DR works.

When you create a Library and then a Project within that Library, are there other folders and metadata at play that needed or else things will break?

Is there a way to make your project/timeline/whatever just all work from some new project directory you create to start with?

Does that mean you trust .DRA archives enough that you would delete your original media, and just grab the archived original media from the archive if needed?

Or is that asking for trouble?

If you're prepared to go into the .dra file, you can confirm that the files are intact -- just load them in a media player.

But only one copy of any indispensable media file is always asking for the trouble. Disks can fail. For anything remotely important, you'd want multiple copies on different disks and/or portable media. And for *really* important stuff, at least one copy off the premises.

For the rest of the discussion, I don't understand what rcmodelreviews is asking for or how it would be an improvement. Archives are self-contained. You create them with two keystrokes, you can move them anywhere with the OS and activate them on any disk from inside Resolve. How much easier can it get?

@John Paines

If you're prepared to go into the .dra file, you can confirm that the files are intact -- just load them in a media player.

But only one copy of any indispensable media file is always asking for the trouble. Disks can fail. For anything remotely important, you'd want multiple copies on different disks and/or portable media. And for *really* important stuff, at least one copy off the premises.

I agree, but that isn't my concern.

My concern - based on a lack of understanding/experience with DaVinci Resolve and .DRA files - is that the .DRA file becomes corrupt somehow, and then I have 20 backups on 20 disks in 20 states of the same unusable garbage!

I think .ZIP files are pretty stable - can't recall in my life of having a corrupt .ZIP from some software snafu. (If you lose a disk sector, this may not be true.)

Not knowledgeable enough to speak about .DR files.

I think the safer approach - if it works - is to save a project in some final resting place along with all free-standing media files and call it a day.

I guess the way you backup a project is via the .DRP file.

Still trying to figure out how DaVinci Resolve actually links active projects/timelines - as well as .DRP files - to the actual media.

For the rest of the discussion, I don't understand what rcmodelreviews is asking for or how it would be an improvement. Archives are self-contained. You create them with two keystrokes, you can move them anywhere with the OS and activate them on any disk from inside Resolve. How much easier can it get?

Because it depends on the mechanics...

If by creating an "archive" (.DRA), all that DaVinci Resolve is doing is creating some parent directly, in essence sticking the equivalent of a .DRP file in this parent directory, and then copying all of the media files into said parent directory, and making it a quasi-file, then I agree that it is simple.

HOWEVER, if DaVinci Resolve is somehow manipulating the original media files (e.g. compressing them) BEFORE it sticks them into the .DRA, then there is a risk that things go South and you *think* you hvae a working, self-contained backup, when instead you have a pile of nothing.

Devil's in the details!

I'll defer to the experts here to explain how DaVinci Resolve works, and try and determine where any pitfalls exist.

What I can say from decades of experience to "It's easy." and "It can never fail" is to raise an eyebrow...

HOWEVER, if DaVinci Resolve is somehow manipulating the original media files (e.g. compressing them) BEFORE it sticks them into the .DRA, then there is a risk that things go South and you *think* you hvae a working, self-contained backup, when instead you have a pile of nothing.

No, I don't think there's any compression involved. It just zips the whole mess. I don't think the folder structure survives, so you basically get all the media in one place. Not sure exactly how that winds up -- I don't use DRA's very much.

I believe it will also give you all the cache files, all the stills, and all the proxy media (if any) as part of the DRA process.

If you want to save space, I'd suggest getting familiar with Media Management (see Marc's advice regarding trim), link your project to the new files and export that project. There's no extra compression going on.
Work with that one from that point in time, frequently save the project, and keep at least one, better two, backups of the media generated by MM.

Hi,

I agree coming from other editing applications that don't work with a database structure, DR can be a bit confusing. Especially where files are stored and how to backup stuff.

But.. As usual YT is your friend. Here's a small list:
- intro in databases and backup:

- transfer projects between computers:

- differences between databases, dra en drp:

- move a project file location:

- databases demystified:

But... My workflow in this is:
- I created a separate DR database on my "Projects' disk, away from the OS disk.
You can have more than one DR DB btw.
- On my "Video' disk, I created a clean (main root) folder structure for my video material.
It's split up between (stationary) corporate indent material, and various separate project folders for the video/images.

That way all the material is to be found in a minimum of locations.
And don't move your data around a lot in folders after you started a project, you will not like yourself.

Lastly:
- I backup the entire DR database location daily, via batchfile to a secondary location.
- if you want, you can export the full database manually as a .diskdb file too.
This only contains all the project data, and just the links to the media.

- I make daily (running) project backups (.drp) You can also set it to automatically make some backups for you.
See the user>backup folder settings.
This .drp file contains e.g. all the edit & timeline data, and only the links to the media. Filesizes tend to be small.

- When finished, I make a project archive (.dra) for archival purposes on a separate, external disk.
This "project_name.dra" folder contains e.g. all the edit & timeline data as a .drp file, -and- all the (copied) media will be in a folder called MediaFiles. Total filesize depends on the amount of media files.

- You can import a .dra back into DR and all media will be there and linked back into the bins and timelines. Be sure to import it back into the proper folder structure. See manual
- You can import a drp back into DR, and as long as all your media is still in the same place, you get a working timeline again. If you moved stuff, you can manually relink it all.

Hope it helps,

rob

Uli,

If you want to save space, I'd suggest getting familiar with Media Management (see Marc's advice regarding trim), link your project to the new files and export that project. There's no extra compression going on.
Work with that one from that point in time, frequently save the project, and keep at least one, better two, backups of the media generated by MM.

Yes, that is good advice that I need to revisit.

However, I will actually have at least two use-cases.

The 1st use-case - which is what I'm asking about here - is for standalone interviews where there is likely one original video file and an external audio file.

I'm just looking for a way to bundle the original media, with the "working files" and with the finished product.

The 2nd use-case, is where I am building this elaborate library of video clips that I re-use. That is somewhat different in that the re-used video clips would have their own home outside of the finished project folder.

It's all a learning process, but I appreciate all of the help so far!

The 1st use-case - which is what I'm asking about here - is for standalone interviews where there is likely one original video file and an external audio file.

You could sync the external audio, replace the audio track with the better one and write it all out in a codec like ProRes 422 HQ.

@robwuijster,

But.. As usual YT is your friend. Here's a small list

Thanks for the links!

Another nuance to archiving in Resolve is if you archive a project where the source media and the destination archive is on the same local drive, the media files are created using symbolic links. Meaning the OS makes it look like there's a copy but it's only stored in one physical location on the drive, making the archiving process incredibly fast and it doesn't take up any extra space. As far as I know there's no way to turn this off (other than to archive/move the archive to another drive).

Another nuance to archiving in Resolve is if you archive a project where the source media and the destination archive is on the same local drive, the media files are created using symbolic links. Meaning the OS makes it look like there's a copy but it's only stored in one physical location on the drive, making the archiving process incredibly fast and it doesn't take up any extra space. As far as I know there's no way to turn this off (other than to archive/move the archive to another drive).

Really? I would not have expected that. Is that a PC-only thing? I was working under the belief that archiving a project copied the media to the dra structure regardless of the location of the archive.

Since it's done at the file system level by the operating system most users won't be able to tell the difference. Functionally it looks and acts like a copy but it isn't. You can verify by keeping an eye on how much space you have left on the drive before and after exporting the archive. Or use the appropriate command in the terminal to list the file properties.

I hope you mean hard links not symbolic links. If so there’s no functional difference and it’s a good thing! If they used symbolic links both copies would be gone if you deleted the original.

@roger.magnusson,

Another nuance to archiving in Resolve is if you archive a project where the source media and the destination archive is on the same local drive, the media files are created using symbolic links. Meaning the OS makes it look like there's a copy but it's only stored in one physical location on the drive, making the archiving process incredibly fast and it doesn't take up any extra space. As far as I know there's no way to turn this off (other than to archive/move the archive to another drive).

Thanks for the info!

I hope you mean hard links not symbolic links. If so there’s no functional difference and it’s a good thing! If they used symbolic links both copies would be gone if you deleted the original.

I think I need to start using DaVinci Resolve, and "learn by doing"...

(Please try to keep the applause down to a low roar!!)

My goal this week is to use my new teleprompter for the first time, and *hopefully* get some usable talking head footage.

But at the same time I am trying to dive into DaVinci Resolve ASAP.

Got lots on my plate with work and personal life, and trying to make all of this come together.

I guess as long as I have backups of everything I can play around with .DRP's and .DRA's and all of my ideas for organizing things, and through trial-and-error, hopefully come up with a safe, secure, reliable, scalable, adaptable, and intuitive data/filing architecture?!

I hope you mean hard links not symbolic links. If so there’s no functional difference and it’s a good thing! If they used symbolic links both copies would be gone if you deleted the original.

Ah yes, thanks for making that distinction. It's hard links.

I just ran into this Hard Links thing (Windows) and I think it's very important to know this is happening - I found out the hard way.

As noted above, if you archive a project to the same volume (drive) that it is currently on, DaVinci creates hard links to the media and DOES NOT COPY IT. I know this sounds good -- but here is the problem:

Since you can't easily see the hard links, it looks to you like you have two copies of the files. This is, in fact, WHY I archived my project -- so I could have an archived copy and mess with the original and not worry about messing anything up. WRONG! Since there is only one file, any edits to the original (or archived file) changes "both" of them on your drive (there is really only one copy). This is not what I'd expect from an "Archive" or backup operation.

I do not believe this behavior is documented - and for the above reason, I think it should be. This could cause someone to have a really bad day.

Lesson learned for me - never archive to the same drive the project media is already on.

EDIT: Figured I should add this so people don't get overly worried: Having said the above, it is true that Davinci does actually copy the project file itself. Only the media files are hard linked. Given that, if you only use Resolve to edit your project, you really can't do anything that would change the media files themselves as Resolve is a non-destructive editor. Using other programs to manipulate files (stills/photos, for example) would have the undesired effect of changing the project and the archives.