Convoluted DNN Upgrade / Migration issue

timruns

timruns

Perch
Hi -- I have an odd situation, I have mentioned possibilites before and gotten interesting & helpful responses, but now am needing to proceed without causeing the client downtime.

I have a client running on a Child Portal of my Service Account DotNetNuke 3.2.2 instance.

I need to move them to their own account and upgrade them to dnn 4.3.5.

I think the best option is to copy the current DNN (DB and folders) and reinstall on a .NET 2 machine, then upgrade to DNN 4.3.5, then delete the DNN portals which will not be used for this client.

Any suggestions? It seems pretty complex to me... I just want to see what others think before I start creating tickets...
Thanks
Tim
 
Yes if you are needing to move them to their own plan the only option will be to copy it all with DNN 3.x that is installed now, then to clean up the portals that are not theirs, then to upgrade. It will eb a long process for sure. Maybe someone else has a better method.
 
Well, the first 1/2 is done (almost). Created the new account, moved everything over (files and DB), then put in a domain name so I could test it. Everything, including all our custom DNN modules worked fine.
There were a few weird/difficult things, but the Jodo folks were, as always, very quick to reply to the ticket and get things done.
Of course, I have some questions as to how the DNS will transfer, but that should be a seperate forum questions...
Thanks.
 
You must log in or register to reply here.
Back
Top