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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...About backup and restoreAbout backup and restore
Previous
 
Next
New Post
1/11/2011 5:14 PM
 
Performing a database restore along with export and import.

Scenario:
Multiple parent portals (separate domains); one DNN install, one database instance

The need to restore; one client's portal ..major discrepancies on edits and whatever other bad thing that can happen from the day before

No problem, database is in Full mode with full database, differential and transaction log backups hourly.

However, a restore to a point in time yesterday will also rollback previous edits of other clients (portals) which would result in an administrative nightmare for those clients not to mention some fancy dancing by me. Not a real good option for all.

Would this be possible :
Export all portals (except the portal of issue)
Perform restore to point of good for the one portal
Import back all portals

Would this work in theory ?

barry
 
New Post
1/11/2011 5:49 PM
 
It's worrying about this kind of scenario that push me towards keeping different clients in separate databases.

I would certainly try this in a test database first.  I have no real idea how far export/import can be trusted. 

As an alternative approach could you recover the database to a point where the broken client is OK.  Export that and import it to your live data (test on a copy first).  Then, I hope, only the broken client is at the risk of any misbehavior in Export/Import. 

Your original proposal puts all the non-broken clients at the risk of Import/Export


Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
1/11/2011 8:33 PM
 
Richard's suggestion will be the best.  Get a copy of the whole db, restore it to the last known good point, export that template then import with replace on.  Extra pages may be present when youre done if they were added after the roll back time.

Philip Beadle - Employee
 
New Post
1/12/2011 11:42 AM
 
Hey Richard

Yeah as I stated,
"However, a restore to a point in time yesterday will also rollback previous edits of other clients (portals) which would result in an administrative nightmare for those clients not to mention some fancy dancing by me. Not a real good option for all."

What you offer is interesting .. Roll back to good ... export portal of issue ... roll forward to current ... import last know good portal data ..
much nicer .. but like you say, if export/import is up to it.

Further.. again providing the exp/imp routines can be trusted, I am thinking along the lines of performing an scheduled export routine for all the portals .. maybe a daily routine .. thoughts??

Also, what are the caveats, if any, to running separate DNN installs as to the number of installs and app pool problems/memory et al.
What's been your experience with this type of scenario?

'working through the love of it all'
b
 
New Post
1/12/2011 3:47 PM
 
It wont help you now but the www.evotive.com solution I've been told handles separate portals for backup and restore.  Im trying to verify that now.

Philip Beadle - Employee
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...About backup and restoreAbout backup and restore


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