> >

Enhancement Details

231

Backup and Restore Management

Provide functionality to perform a full site backup and restore including all web files and SQL database. Backup task could be scheduled through existing DotNetNuke scheduler.

Problem:
Frequently in shared hosting envrionments, backup and restore can be an issue and many hosting companies charge to perform a database restore.

Rationale:
This enhacnement will make DotNetNuke self-contained removing the need for additional tools etc to manage hosted instances.

Solution:
Include Host functionality to, - Create a site backup task - Schedule backups - Provide ability to restore - Manage backups (eg delete old ones after a certain period)

Impact:
New functionality

Risk:
Low risk

Created: 6/3/2007 9:16:38 AM by Paul H
Scheduled For Version:
Delivered In Version:

Return

Comments

You Must Be Logged In To Add A Comment

Angus Beare
11/1/2011 7:10:52 AM

I use Evotiva. It's a very good module and quite mature now.

Something like that and integrated into dnn and free would be lovely! But that's a lot of code for free!

Scott S
10/30/2010 1:49:09 PM

In building this solution it is important to keep in mind how to restore when DNN is not functional for some reason. It's nice to have a backup/restore when something doesn't go as planned, but it's essential to have the restore ability when a site is totally down.

I recently saw someone depending entirely on a 3rd party backup module discover that restore is a real problem when the site doesn't work at all.

Gary Herbstman
2/22/2010 10:00:55 AM

Options to include the installed modules and templates that are required for the portal would be a big plus for migrating to different hosts.

Horacio Judeikin
6/2/2009 5:17:27 PM

and already exists BackupScript (http://tinyurl.com/BackupScript) for most shared hostings, like GoDaddy, where BackupNative will not run. Individual portals backup/restore is in its roadmap

Reuven Chapman
1/17/2008 10:33:12 AM

I feel very strongly that DNN needs an integrated Backup/Restore utility.

One more point I want to add to the comments already made is that it should be designed to be integrated also with the DNN Upgrade wizard as well as the Module/Skin/Container Upload utility so that it will allow the user to elect to perform a complete backup before proceeding with DNN Upgrade or the Module Upload. Also, if the Upgrade or Upload fails; it could offer to do a restore from Backup before returning to the main menu.

I also agree that it must be able to run in a GoDaddy or other shared hosting platform.

Alex Shirley
7/25/2007 6:31:49 AM

Also see http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=5659

Mauro Miotello
6/19/2007 10:06:52 AM

A full site backup like BackupNative is useless !
In a DNN instance with multiple Portals, we need a feature to backup/restore a single Portal or multiple Portals each with your own file.
Every backup file must be contain all db records and all related files !!
I think that with the actual DNN structure do this feature is very very hard !
How many Professional webmaster are using multiple portals for each DNN istance ??

Jeff Parker
6/18/2007 10:15:56 PM

A request please. Can the planned backup function not only backup the DNN db but also any others used in the site that the admin specifies? I have an app embedded in my DNN install that uses a separate SQL database and I'd like that backed up at the same time as the DNN one along with the folder hierarchy. I'm guessing this is not that an unusual config.

Philip Beadle
6/18/2007 6:35:50 PM

Another feature of this would be cool if we could do a portal by portal backup as well. A bit like the Export Template.

milton allione
6/14/2007 11:24:29 AM

This functionality already exists in 3rd party module BackupNative, exactly as suggested.

The unfortunate part is that DNN does not allow the user to set a start time, or frequency for a scheduled event ... only an interval from the time the last event fired.

Philip Beadle
6/13/2007 10:36:45 PM

As an addition to this it would be great if DNN could do an auto backup when a module is installed or an upgrade is triggered. This would make roll backs really simple if either case fails.

Hosted by MaximumASP