<!--[if gte mso 9]> Normal 0 false false false MicrosoftInternetExplorer4

<!--[if gte mso 10]> Peter,

 

Our developers need to practice moving the DMX documents from one server (one DNN instance) to another server (Another instance). The server to move to is not a duplicate copy of the current one. I couldn’t find an online documentation to follow. Can you provide guidelines for the following 2 possible scenarios?

 

1. If we only need to move folders and documents from one DNN to another DNN instance on another server.

 

2. If we have a backup copy for a DNN instance, when this instance is restored on a new server, how will the DMX behave ?  Will it behave the same way as it was on the original server, or any steps to follow to configure it?

 

Thank you

Hi,

The first thing you need to realize is that 2 DNN installations have 2 different sets of users and roles. They may be called the same, but there is no direct link between them. User ID (the internal numbering of users) and Role IDs will probably be different. Similarly module IDs, Tab IDs etc are also different. What this means is that moving data from one installation to another cannot be done by passing data. DMX data ties in to users and roles and therefore the data would be useless in the receiving installation.

So the only option there is, is to step down to what we all know: folders and files on our PC. You can export data from DMX 4 by selecting to zip up a directory and download. Keep an eye on server request timeouts (you might need to increase that). Once you have the zip you can unpack that somewhere on the receiving server and import it into a folder. For now it cannot be done smoother.

We are working on synchronization options, but this is still some time away. Like I pointed out above, it is not trivial and needs careful work.

Kind regards,
Peter

Thanks, peter. I understand the situation on roles, users, etc that will make the data migration a difficult process for 2 different DNN instance.  What if we just look at the picture of a disaster recovery? i.e. recovering the folders, files, DMX modules, etc all along with a new DNN instance which shall be the identical to the LIVE one.

Has this been tried out on your end? Shall the DMX behave exactly the same after the recovery?

Thank you

 

 

Yes, it shall. For disaster recovery what you should do is to regularly backup all the DMX_ prefixed tables (or your whole DNN database of course) and the portals/[portalid]/DMX folders. You could schedule this on your server. Then, in case of emergency, put the tables back and the DMX folders and all should be as before.

Peter