As MAM managers you may decide that assets from some projects in Zoom may be less relevant and could be archived to a low-cost tape storage whereas assets from some other projects may have to be kept much more accessible in say, a high-end SAN. You could achieve this functionality right out of the box with Zoom 7.1 and above.
Check configuration details here.
Enter the Zoom paths and their corresponding file system locations to which assets must be archived to.
For example, the entry may look like this on a Linux server:
/defproj=/data/Archives/misc/ ; /Library = /mount/commons
And like this on a Windows server:
/defproj=\\NY-NAS\backups\defproj; /Library=L:\Users Data\Users1\akila\Others
At this point server.xml will show a new entry in <archivespec>, <targets>
<targets>/defproj=\\NY-NAS\backups\defproj; /Library=L:\Users Data\Users1\akila\Others</targets>
The paths may be a mapped drive letter path or a UNC path, or a local or network file system path. As long as the Zoom server process has the correct permissions into the target locations, the archive operations will work just fine.
Any assets belonging to paths given here, will get archived according to the locations configured here; the assets belonging to paths not mentioned in this field, will still get archived into the default archive location.
Though it is usual to put the paths corresponding to Zoom projects here, it is not mandatory. You could specify any folder path in the configuration and partition your archive locations even within the project-level boundaries.