Content Move job - Multiple jobs for the same condition
Hello Experts,
We have a situation to quickly release the current storage and use the new storage. We have scheduled Content Move to move documents. We currently have 20M documents and with the current speed, it seems, it will take months to move the documents to the new storage. We have following questions and would like to have your quick response.
1) Can we configure more than one job using the same condition pointing to the same storage?
2) Will there be a conflict if we run more than 1 job?
3) If multiple jobs can run, how many jobs would you recommend to run in parallel?
4) We have two Frontends and 1 Admin Server. Is it possible to run the job specifically to a node?
5) Any other option to increase the speed from the application side would be of great help.
Appreciate your kind support.
Answers
-
Thanks for posting @Raeez , are you using Content Server or Documentum Server? I can move your question to the category where the experts can help out.
0
Categories
- All Categories
- 118 Developer Announcements
- 52 Articles
- 150 General Questions
- 137 Services
- 56 OpenText Hackathon
- 35 Developer Tools
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 912 Cloud Fax and Notifications
- 82 Digital Asset Management
- 9.3K Documentum
- 30 eDOCS
- 175 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 6 XM Fax