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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Move/Restore DNN Site from DevServer to ServerMove/Restore DNN Site from DevServer to Server
Previous
 
Next
New Post
4/27/2007 5:14 PM
 

My setup is like so:

Dev Machine: XP Pro, VS.NET, SQL Server 2005

Server: Server 2003, SQL Server 2005

Two days ago, I had fully functioning replicated DNN sites. One on my DEV machine connected to a test database on the remote SQL Server, and one on my live web server, connected to the live database. The databases essentailly contained identical data, but I am nervous about creating an error I can't solve, so I have two dbs.

Then for seemingly no reason, the DEV version image link broke, and all items on SOLPART menu were duplicated (each appeared twice).

If I switch PortalAlias value in the test site db to the live site url, all works fine. If I switch it back to 'MyDEVMachineIP\app_name' I get broken and duplicated links again.

I have tried copying the live db and changing the Portal Alias value, I have tried creating a new db and running the install.aspx file and then import the data from the live db, and nothing works.

Also, if I have the dev site running so that the links are broken or duplicated, no login work anymore. Neuther host nor admin, and, if I click  'Send Password', I get 'There was a problem retrieving the username. Password was not sent'

 

Oh, if I try to simplify, and just copy the live, working db, and point the DEV site to the copy, and edite the portal alias to my local machine, I get

The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.


    *   This problem can sometimes be caused by disabling or refusing to accept
          cookies.

 

Any ideas?

 
New Post
4/27/2007 5:59 PM
 

Hello - I am not completely understanding your setup, but if this has been working for you in the past perhaps it is the best way for you.  Are you saying you have duplicate data on your remote database used in your dev environment?  How are you replicating your data?  Is one a master and the other a slave, or are both sync'd with changes merged on both instances?  Do you have the same object qualifier for your server objects?

I am not  a big fan of replication, especially if it is setup using an MS SQL Server wizard, and replication between two database servers could be dangerous, or at least tough to do.  My recommendations would be:

  1. Export your live site using the Portal Alias utility while logged in as host.  Export the content/data with the template.
  2. Setup a temporary Dev SQL Server and create your portal siet using the export from (1) as your portal template.and keep the portal id (0,1,2, etc.) the same.
  3. If possible create a maintenance plan on both servers so you are backing up your data on a regular basis.
  4. Review your replication techniques or dump replication all together and use sql scripts to push data between sites if possible.

It sounds like you have one good database, so you should not be in bad shape.  Replicating data can get tricky rather quickly, but it is certainly done and nothing new.  There are three types of replication that MS has wizards for but additional keys are added to your tables to hold GUIDs used by the replication mechanism.  Merging data so each site is essentially a copy of the other at a future point in time requires the use of rules to determine which data source wins when there are data conflicts (i.e. same record updated by two different people).  Transactional is immediate but there is overhead and potential locking.  The master-slave scenario can potentially delete information on the slave db, and will add new records as needed.

We probably all have had data go bad on us. I just recently had a server taken off-line w/o warning and with my database on it!  I had my backups copied to my home directory, though, as I sensed this might happen.

Good luck and hopefully you can recover from your live site!

John

 
New Post
4/27/2007 6:07 PM
 

My explanaition probably was not very clear as I am pretty confused myself at this point.

Essentially, what I want to do is have two identical copies of my DNN site. One on the server and one on my dev machine. Since I feel that it is really easy to break the site, at least for a rookie like myself, I also want two copies of the database....on connected to the live site and one to the test site. That way I can test as I please without having to worry about breaking the live site.

I had this exactt setup working a few days ago, for several days, but then suddenly the image links and broke and the menu items each appeared twice. I can't figure out what happened and I can't restore the test site using a copy of the live database because I keep getting the 'Firefox is being redirected in a way that t will never complete...."

I don't want to develop and debug on the live site so what should i do?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Move/Restore DNN Site from DevServer to ServerMove/Restore DNN Site from DevServer to Server


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