You are viewing limited content. For full access, please sign in.

Question

Question

Copy production repository to an existing test repository

asked on June 26, 2019

Hello!

We have a customer that is wanting to test 10.4.1 before implementing it. We've set up a test repository for them a few months back, but it's now out of date with their production environment. I've read up on how to duplicate a production environment into it's own repository, but that seems like overkill in this case. Is there a simpler way to just copy the production environment into an existing repository?

Regards,

Peter

0 0

Answer

SELECTED ANSWER
replied on June 26, 2019

Trying to "copy" a repository into another is not a quick or easy task.

You want a copy of your existing repository, so you need to make a new copy of the repository on the test LF server.  This will ensure that you have an exact copy and will go easier and faster than trying to sync 2 existing repositories.

2 0
replied on June 26, 2019

That's fair. I had a feeling that would be the case, but I just wanted to double check. Mostly I wanted to avoid touching multiple potential failure points like forgetting to set up the new WF subscriber or something. Just figured that keeping a test repository up to date might be easier than a full replication.

 

Thanks for the input!

0 0
replied on June 26, 2019

Keeping 2 repositories in sync is doable, but there are a lot of pitfalls and scenarios to work through.  Since this is production and test, I am guessing that the it does not need to be a 2 way sync and that makes it easier.  You can create a workflow that copies entries from production to test on creation, but then how do you deal with modifications to entries?  All sorts of things can happen that will get everything out of alignment.

1 0
replied on June 26, 2019

Absolutely. My initial thought was to actually just wrap up the whole repository in a briefcase (it's fairly small at the moment) and import that to test, but I've had issues with briefcases not keeping Records Management settings in the past.

If this is going to be a regular thing that the customer wants to do, I may just end up making a workflow for it. Thinking up solutions for fringe cases is pretty much my job description, after all!

 

Anyway, thanks again for the assist, you've given me things to think about!

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.