The API methods, archive and restore, are used to fire archiving
and restoring tasks into the Inbox for dm_DMArchive job to read.
The dm_DMAchive job calls the dm_DMarchive method. And then
dm_DMArchive method calls the dmarchive tool to do the archiving or
restoring job. The dmarchive tool will run on the content server.
Therefore, an archive directory on the content server needs to be created
and also specified in -archive_dir parameter before you run the
dm_DMArchive job. For example, -archive_dir C:\myarchive
When you
use API to fire an archive task into the Inbox, you can select different
groups of content files being archived. Use API dump method to verify.
For
example,
API>archive,c,dm_document
where owner_name = 'username'
API>dump,c,l
API>dump,c,l
This will
fire an archiving take for all the content files belonging to the user.
You can use the similar method to archieve different groups of contents.
For more details, please refer to the Content Server Admin Guide from
page 284.
After you run the dm_DMAchive job setting -do_archive_event TRUE, you should be able to see a new file in that archive directory on the content server. And also notice that you cannot open the file(s) using DA/Webtop after you run the dm_DMArchive job successfully. DA/Webtop will tell you that "Content object ********* is offline".
After you run the dm_DMAchive job setting -do_archive_event TRUE, you should be able to see a new file in that archive directory on the content server. And also notice that you cannot open the file(s) using DA/Webtop after you run the dm_DMArchive job successfully. DA/Webtop will tell you that "Content object ********* is offline".
When you
restore an archived content, you can simply send the archived file back
to the archive_dir, run API restore and then run the dm_DMArchive job,
but specify -do_restore_event TRUE.
For
example,
API>restore,c,dm_document
where owner_name='username'
API>dump,c,l
API>dump,c,l
Use
DA/Webtop to check if the content of the restored file can be accessed again.
After a
task of archiving or restoring is fired, you can also run dmarchive tool
directly from the command line on the content server.
C:\Documentum\product\5.3\bin>
dmarchive <docbase_name> -U<docbase_owner> -P<docbase_owner_password> -archive_dir <full_path_name> -do_archive_events|-do_restore_events -verbose
dmarchive <docbase_name> -U<docbase_owner> -P<docbase_owner_password> -archive_dir <full_path_name> -do_archive_events|-do_restore_events -verbose
For
instance:
Archive:
dmarchive DOCBASE
-Udmadmin -Ppassword -archive_dir C:\myarchive -do_archive_events -verbose
Restore:
dmarchive
DOCBASE -Udmadmin -Ppassword -archive_dir C:\myarchive -do_restore_events
-verbose
Symptoms
Archived
the files cannot be found.
Cause
The
directory specified in archive_dir does not exist on the Content Server.