Archive Service
Get the answers to frequently asked questions about the DNAnexus Archive Service
Last updated
Get the answers to frequently asked questions about the DNAnexus Archive Service
Last updated
Copyright 2024 DNAnexus
A license is required to use the DNAnexus Archive Service. Contact DNAnexus Sales for more information.
The new Archive Service was released on November 1, 2019. The differences between the old and new versions can be summarized as follows:
Old Archive Service
New Archive Service
Project-based
File-based
Works only on projects
Works on files, folders, and projects
DNAnexus-assisted
User-directed
APIs are not accessible to users
APIs are accessible to licensed users
Complicated process (see figures below)
Simplified process (see figures below)
Files are automatically archived when moved into an archived project
Files are archived at user request
First, if you were using the old Archive Service, there will be no impact to the files that you have already archived. Second, files that you move to old archived projects will not automatically be archived any longer. Alternatively, you can use new Archive Service to archive the original project periodically; the platform will archive all the live files in the project and skip files that have been archived. And finally, you will no longer need to create a special archived project to archive or unarchive files any more.
No. Only those users in the project with CONTRIBUTE and ADMINISTRATOR permissions to a project can archive or unarchive files that reside in the project. For the -allCopies option, users must have the org-admin role for the billTo org of the project.
The copy that is initiated for archiving will transition into the “archival” state, and the other copy will remain in the “live” state. You will incur a standard storage rate for one copy of the file size. If the second copy of the file is called for archive, the file will first transition to the “archival” state. Because all the copies of the file in the same billTo org are requested for archive, the file will finally be in the “archived’ state and moved to the archival storage and incur an archival storage cost for one copy of the file size.
CopyA of a file in ProjectA in billTo OrgA
CopyB of a file in ProjectB in billTo OrgA
CopyC of a file in ProjectC in billTo OrgB
Cost for OrgA
Cost for OrgB
live
live
live
1x standard storage cost*
1x standard storage cost
live
live
archived
1x standard storage cost
1x archive storage cost
archival
live
live
1x standard storage cost
1x standard storage cost
archival
live
archived
1x standard storage cost
1x archive storage cost
archival => archived **
archival => archived **
live
1x archive storage cost
1x standard storage cost
archival => archived **
archival => archived **
archived
1x archive storage cost
1x archive storage cost
* - Storage cost for 1 copy of the file
** - The first copy of the file has been requested to be archived and in archival states, when the second copy of the file is requested to be archived, the second copy of the file will transiently transition to the archival state. Because all the copies in the billTo org are in the archival states, the system will transition the file into the archived state.
If all the copies of the file in your billTo org are all requested to be archived, the file will be transitioned to the archived state, and you will incur an archival storage rate, while the file in the other org will still be in the live state and incur a standard storage charge in the other billTo org.
You can do this using the “-allCopies” option but you must be the org-admin to do so.
No. In the new Archive Service, we don’t label the archive state of a project. All projects, which are containers for the files within them, are the same.
These resources provide more information on the Archive Service and how to use it:
