It is always fun when you are involved in migration. Ok, here is there situation. We want to move the ucm content from one server to another server.So what I am supposed to take care?
Before jumping into action, you need to understand the state of source and target machines. In my case, my target ucm server has some content and I want to upgrade the targer with source content.
Now the question is, is it ok to upgrade just content? definitely NO. You need to make sure that source & target servers are synchronized with meta data, security (roles & accounts),workflow definitions etc. If not, you should do that first by using 'Content Migration Utility' or from admin console, you can use content migration section to do it.
The steps are,
1. Migrate meta data,security,workflow using content migration utility.
2. Migrate content using archiver using admin applets from admin console.
Let's see how to migrate using content migration utility:-
1. Go to administration console of source machine.
2. Create or Update configuration migration template. Go to Administration -> Config Migration Admin -> Configuration Templates
3. If there are any previously used template, then edit the template to see the configuration.
4. Otherwise, ‘Create New Template’ from Action drop down.
5. We are going to edit existing template.
6. Click on ‘Content Server Sections’ to review the selected items. You can go to ‘Preview’ from Actions drop down to see complete picture.
7. Now click on ‘Export’ to export the selected items to bundle. You will be redirected to ‘Latest Action’ page where you can see the progress.
8. Wait until you see ‘Finished in the message.
9. Now go to ‘Administration -> Config Migration Admin -> Configuration Bundles’.
10. You will see the bundle created with recent date & time.
11. Click on ‘Download’ from the drop menu and save the zip file in local file system.
12. Now go to the target server. Go to Administration ->Config Migration Admin->Upload Bundle.
13. Now upload the zip file which was downloaded previously and select the options as shown below. And click on ‘upload’.
14. In the Configuration Bundles page, click on the one which was just uploaded.
15. Now select drop down to preview.
16. Select ‘import’ from drop down.
17. You will be redirected to ‘Latest Action’ page and you can see the progress of import.
We are done with meta data migration. Now we can migrate content using archiver. I assume that you have already defined outgoing providers from stage to production.
1. Go to ‘Administration ->Admin Applets’. Then click on ‘Archiver’.
2. In the archiver, Go to ‘Options -> Open Archive Collection’. Then select the collection you want to use. You should be able to see production instance in the list and select the instance you want to use & click ‘Open’.
3. Go to ‘Edit -> Add’ to add new or update existing archive. Click ‘OK’.
4. Now newly created archive will be highlighted and review ‘Export Data’ tab settings. Click on ‘Edit’ button and select ‘Custom Query Expression’.
5. Let’s use custom query to fetch content created after 07-Mar-2011. The query will be dInDate > {ts '2011-03-07 00:00:00'}.
6.6. Select ‘Export Revisions with Release Date later than most recent Export date’.
