Edge Archive (separately licensed application)
A separately licensed application that creates a real time data Mirror of the Project from the two Client Deliverable folders and the Raw editable Project within Edge DVR if required.
EdgeDVR Archive - Realtime Data Mirroring
Edge Archive is a separately licensed application that creates a real time data Mirror of the Project from the two Client Deliverable folders and the Raw editable Project within Edge DVR, allowing for a Projects media to be removed from the DVR, whilst maintaining the structure and integrity of the Project. This means the Project itself does not have to be deleted to free up space on the internal storage.
It allows for:
- Simple data mirror
- Phased delivery
- Multiple copies of the Deliverable
- Simple / Complex data archiving
Simple data mirror
In Use cases where all data for a project fits on the 4U/Laptop internal drives: Ie The user requires a complete copy of the raw project data and the operations/inspection deliverable at the end of the project. The user doesn’t have time for a complete copy during demob so uses Archive to make a real time mirror of the raw project and deliverable data.
- Two archive destinations: one for raw project data and one deliverable data
- Each archive destination has a single archive folder on an external device (NAS, USB hard drive etc.).
- At the end of the project, once archiving has completed all data is set to offline and archive folders are ejected. The user then closes Archive then deletes the original project using DVR.
Ie All data for a project fits on the 4U/Laptop, but the user needs to deliver data to the client after each dive. Another arrangement (e.g. that outlined above) is in place for backing up data at the end of the job.
- One archive destination for the operations deliverable.
- One archive folder for each Dive (or however many dives the client needs grouped together). Each archive folder can be on a separate external device (NAS, USB hard drive etc.) or multiple archive folders can be on the same device.
- After each dive (or however many dives the client needs grouped together) the user creates a new archive folder, sets the existing dives/folder offline, then ejects the old archive folder. The device containing the ejected archive folder can be handed to the client while new data is copied to the new ‘active’ archive folder.
Multiple copies of deliverable
All data for a project fits on the 4U/Laptop, but the user requires one copy of the deliverable on a shared NAS, and two further copies of the operations deliverable on external USB hard drives. The shared NAS is large enough to hold all the data, but multiple USB hard drives are required.
- One archive destination with a single archive folder on the shared NAS
- One archive destination for deliverable “copy A”, with an archive folder on the first batch of external USB drives.
- Another archive destination for deliverable “copy B”, with an archive folder the second batch of external USB drives.
- As each external USB drive fills up, it’s data is set offline, then the folder is ejected and shipped back to the beach.
Simple data archiving
The 4U/Laptop does not have enough space for all project data, however a large external storage device (e.g. NAS) is available.
- Three archive destinations (raw, operations, inspection), each with a single archive folder on the NAS, are used.
- The user records, processes and reviews data using DVR as normal.
- Once a dive has been processed & reviewed the user sets it offline. This automatically deletes the data files from the 4U/Laptop.
Complex data archiving
As for “simple data archiving” above, but each archive destination has multiple archive folders. This may be required if all project data can’t fit on a single external device (e.g. no NAS available, very long project etc.). External devices may be ejected when they are full to free up USB ports.