Implementation of Documentum DR

Hi friends,

We in our organization are planning for a DR. I had suggested an senario, i would like to ask your suggestion on the senario. the senario i suggested to install a content server on secondary site and then we are planning to restoring the file system and the database on the secondary site.

We in our organization also have a Centera Archival storage which is at primary site and also have a replicated CAS on secondary site. My question is i would like to ask you how can we connect the Secondary Site content server to the CAS at secondary site. So, that i can access the archive content from the secondary CAS site.

Here i am using same docbase id for both repositories.

Regards,

Purushotham Ch

Find more posts tagged with

Documentum

Comments

DCTM_Guru

If the content server has the same server name as the primary, then you should be fine. Look at the cloning procedures in the install manual. The strategy is basically the same.

purushotham_reddy

Hi Johnny,

Thanks for your reply.

Is there any posibility to have a DR with different server name on secondary site and Content Server installed on the system and also having same repository ID as primary. In this case can we implement cloning and restore Database and filesystem in same path, can we do successful implementation of DR.

Regards,

Purushotham

DCTM_Guru

This would require you to change the host name in the dfc.properties file at the very least. There might be other changes you would have to do as well. Look at the cloning procedures for the prerequisites to "restore" to different environment.

If the DR site is on different subnet, having the same server name was not an issue.

purushotham_reddy

We have centera archival storage at both primary and seconday site which is replicated on daily basis. We have a created a Centera Store on primary server. Can we use the same Centera Store can be connected to secondary site on change on .pea file.

DCTM_Guru

Replicating the dfc.properties file doesnt resolve server name difference if the server name at DR site is different from your primary server.

purushotham_reddy

From the descition i got to know that we need to have same server name on both the system to clone.

Now the thing is not about Server name or dfc.properties. We have a centera store on our primary server which will also be on DR server on cloning of Docbase or repository. The centera store has the primary centera store storage parameters and .pea file.

If i change the storage parameters and .pea to the secondary centera storage which has all the back replication data of primary centera storage of the centera store storage in the cloned DR server. Can i access the archived files whithout any problem.

DCTM_Guru

I dont know specifically about Centera, but we do DR by replicating filestore and database from primary to secondary site without any issue.

purushotham_reddy

Thanks for your reply.

Elliott

We use Centera for our compliant storage and have a DR site. The data is copied to the Centera device at the DR site by SRDF. The DR network is not connected to the primary network, so that when we bring up the DR site the Content Server uses the same .PEA file and the same IP addresses for the Centera devices as we use in Production. Note: we also use the same database name as in Production (the database file systems also use SRDF to copy them to the DR site, so that the database is exactly the same when we start up the DR Content Servers). The Content Servers have different names, but we use DNS to trick Documentum into thinking that the CS server names are the same. The only software that had an issue was FAST - we had to rename the log files that had the server name in them to the new server names, before it would start. Since we're using xPlore now, that doesn't apply.

DCTM_Guru

Thanks Elliott for confirming this and providing details