Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Migrating DNN from dev to live environmentMigrating DNN from dev to live environment
Previous
 
Next
New Post
11/7/2006 8:01 AM
 

I have configured an installation of DotNetNuke v4.3.5 in a hosted developer enveironment provided by my hosting company. I am ready now to migrate this installation to my live server (a shared hosting environemnt with a seperate IP than the develpment environment, but 'under the roof' of the same hosting company). I therefore requested my host's help desk to migrate this DNN install (& database) to the root of my shared hosting account. However helpdesk replied saying this would be difficult / impossible as:

"The problem with DNN is that it hardcodes the IP address it is being installed on, into the DNN portal, and it always breaks anytime someone tries to move it."

Is this true? If so can anyone here advise what is the best way forward? I understood that migrating a DNN portal from one IP nbumber to another was possible (or is possible but problematic).

Any advice appreciated. Thanks.

Eoghano

 
New Post
11/7/2006 8:56 AM
 

Eoghano,

this is simply rubbish. You move your site as follows:

  • add the new address as portal alias to your site (host >> portals, select portal, add alias at the bottom)
  • make sure, there are no links (e.g. in HTML content) using old full URL
  • backup your installation folder (where the web.config resides) and database (if it gets moved as well)
  • restore database (if moved)
  • setup IIS web and folder permissions
  • restore installation folder
  • if db moved: adopt connection string in web.config
  • hit your homepage.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/7/2006 9:41 AM
 

Thanks Sebastian,

I pointed my hosting company to your advised steps and they then replied to me saying:

"While this does seem possible, we will not gaurentee that even if we attempt this procedure that you will not lose the data anyway.  As previously stated we have not seen a sucessful move of DNN to a new server."

Have migrations been this problematic in the past? Has anybody experience of a migration that went without a problem?

The hosting company in question BTW is a DNN sponsor...

Eoghano

 
New Post
11/7/2006 10:41 AM
 

As long as you are transferring a complete installation (not only a portal out of it), it is not unusual business IMO.

And hay shall you loose data as long as you are creating a copy and install it on a previously blank server?


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/7/2006 10:43 AM
 

I have to second Sebastian's words -

Not only did I have to migrate my sites from a windows 2000 server to a windows 2003, I had to create new folders, new naming conventions, change IP addresses for about 200 clients. It took me some time to sort out a couple of things - like - xml files that were reading wrong folders on a 2.1.2 site but if your hosting company is using virtual directory eg.. domain.com/portal - rather than domain.com (which is what I use) then maybe there is something I don't know about.

But i've also developed sites locally for clients, then delivered to them via email, portals they just attach and it's a site to go..

I think your hosting company just doesn't want to do it - but if you're only paying a couple of dollars per month - then it could be one of those hard jobs they find isn't worth their money.

I can assure you that DNN does migrate and it's been easier for me to move my DNN sites to another server than some of the older asp ones.

So, look for an other hosting company if it's too hard for them.. and just because they're listed here doesn't mean they are endorsed by DotNetNuke - they pay to advertise here.

Sorry if I seem a little .. testy .. in my attitude - I just find it frustrating at times with the misinformation out there to confuse or trick people into thinking these things.  And.. I'm not an IT techie - so if I can do it surely a 'professional' hosting company should be able to.

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Migrating DNN from dev to live environmentMigrating DNN from dev to live environment


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out