Start a Conversation

Unsolved

This post is more than 5 years old

KT

601

March 7th, 2006 02:00

retrieve DX managed files from site B which were archived on site A?

Brief site history:
There are two client sites. (a) Site A and Site B. Site A contains a AX/DX server by the name of VPIDMS1 with an EMC Centera. Site B has a AX/DX server by the name of VPIDMS4 with an EMC Centera. AX, on Site A, will archive data using DX to Centera.

On Site B, I want the data that was archived on Site A. So, we will use RepliStor to replicate data from Site A to Site B (replicating meta-data information and the stub files that DX has produced on Site A over to Site B).

What I wanted to do was following:
1) Archive some images using AX and put it in a media folder managed by DX (media folder's name is AXDATA).
2) DX will write to Centera and purge leaving the stub file on the media folder. Also the meta-data export will be scheduled to be exported to site A's server.
3) RepliStor will be installed on both the sites and the DX meta-data information and the stub files will be replicated from Site A to Site B.
4) After the replication is complete, the meta-data from site A will be imported to Site B using the Meta-data import wizard.
5) The meta-data import worked fine but it doesn't create the proper information on Site B for DX to know that the stubs are already replicated and they are in the media folder on Site B.

How can i do this? Is it possible to use the DX managed files from Site A to Site B without DX actually managing the files again once the meta-data information is exported?

March 7th, 2006 19:00

Can anyone help me on this issue?

THanks.

4 Posts

September 13th, 2007 14:00

Hmmm,
In my opinion You should use DX to manage files separetly on sit A nad B.
Just firs replicate them with Replistor, then DX will write data to proper centera.
Please let me know if this answers your question.
Michal

8 Posts

December 31st, 2008 07:00

It has been almost 2 years since your original post, but here goes my question.

Did you ever find a resolution or get help with your issue? We have the very same configuration and process going on, except I have not begun to replicate the Stub Files with RepliStor from Site A to Site B yet, until I'm 100% confident that the files will be retrievable from the secondary Centera at Site B, which is running bi-directional replication with the primary Centera at Site A.

9 Posts

January 13th, 2009 15:00

The problem with using Meta-data inport is that the servers need to be named the same. We have also found many issues with RepliStor.

The best solution is to have the second server with a different name. Install everything on that second server exactly like the original. Perform exports of the DX registry hive from the production server. Open the exported registry file and make the following changes. Modify the IP addresses or alias name for the Second Centera. Modify the Server name from the original to the second server. Stop the DX service on the second server. Import the registry information to the second server. Restart the second server. Open DX Admin. Right-Click on each Media and perform a file restore. This will pull all the Stub files from the second Centera to the second Server. You can do what you want from this point including deleting files (beware that if you have bi-directional replication turned on between Centeras, you will delete Primary Centera Data, so be careful!!!!!)
No Events found!

Top