0
votes

I've tried many things suggested around the web and have not been able to clone a DNN site with total success (just partial, glitchy clones):

On sandbox server:

  1. Back up DNN DB

  2. Back up DNN files from IIS

On production server:

  1. ​Restore DNN DB from step 1

  2. Host DNN files from step 2 in a new IIS site, using same app pool & security settings, etc.

  3. Do basic housekeeping, change DB connection strings in web config and update portal aliases, etc.

  4. Log in to new DNN site on production, which should be an identical clone of the DNN site on the sandbox... Doesn't work!

Is there no way to get this to work with DNN?

2

2 Answers

0
votes

That process should work for dnn just fine.

What about the restore isn't working? Are you sure update portal alias and then start the application? If you update after the app starts you need to restart the app.

0
votes

I would also update the DefaultPortalAlias entry from the PortalSettings table:

UPDATE PortalSettings SET SettingValue = 'www.YOUR-DOMAIN-GOES-HERE.com' WHERE SettingName = 'DefaultPortalAlias'