Backup & Restore in a null sheet
Install the module as any module (from Host > Module Definitions), with no special consideration and add it to a not publicly available page.
To backup
By default a ‘full backup’ (database and files) is configured. There is no need to ‘mandatory’ change any setting. If the module guesses that native backups can be performed, that would be the default choice.
The module will not allow you to enable settings that it guesses will not work in the current environment. I.e. “script database objects” or “ftp transfer” when not running in a Full-Trust hosting environment.
Note: We've designed the module to be as much self-explanatory as possible.
To restore:
This can be on the already running site (the same where the backup was created) or could be an empty web site (no DNN and blank database).
a) Running DNN: On the module’s main page, there is a button to trigger the Restore Wizard.
b) Blank (empty) web site: Decompress and upload the “Restore_Pack” to the (blank) web site’s root. Browse to http://my_site_url/backup/
If “default.aspx” was configured as a default document for the site you’ll be redirected to the restore wizard page. If “default.aspx” is not a default document for the web site you can manually browse to the restore wizard: http://my_site_url/backup/RestoreWizard.aspx or http://my_site_url/backup/default.aspx
Note: The restore pack includes a 'This web site is undergoing scheduled maintenance' default.aspx page for the web site's root.
The Restore Wizard will guide you on the steps needed to perform the chosen operation. It should allow you to perform only operations it thinks will be able to accomplish.
About database objects backup methods
There are three methods to get the database structure (the module supports all, but the running environment may not support some of them):
- Native SQL Server Backup: this is the preferred method and you will get an exact 1:1 copy of the full database (structure and data). This method is available for “local” databases (web and database servers are the same box) and proper database access permissions are needed.
- this will not work at GoDaddy -
- Script Database Objects: this method will script all the database objects on the database, whether the DNN core, 3rd party module or any other means created them.
Even if this method is available, it is recommended keep “Save DataProvider Files” enabled. “Save DataProvider Files” will backup and restore the objects a lot faster and it will enable change the “ObjectQualifier” in case is needed.
- “Script Database Objects” will require “Full Trust” and it will not work at GoDaddy-
- Save DataProvider Files: this method saves all the “SqlDataProvider” files (core and 3rd party) enabling the creation of all these objects at restore time. If there were other objects in the database that were not created by this standard and recommended method to create database objects in DNN, their structure will be missing. Note that the core 100% sure will be re-created and regarding 3rd party modules, every “well made” module will include all its database objects in “SqlDataProvider” files.
By the way, this method enables changing the “ObjectQualifier”. If in the source server was defined i.e. a “dnn_” object qualifier, at restore time this can be changed to anything else (even leave it blank).
- this will work on any ISP, including GoDaddy –
FAQ
Q: Sometimes the backup cancels with error "Thread was being aborted."
A: Please try this change in your web.config file:
<httpRuntime useFullyQualifiedRedirectUrl="true"
maxRequestLength="88192" requestLengthDiskThreshold="88192"
executionTimeout="108000" shutdownTimeout="108000" />
Q: Sometimes the backup schedule is duplicated (it runs many times).
A: This is a known DNN bug (versions < 5.2.3). In DNN Backup (4.2+) we've implemented a workaround for this problem. See: DNN Support (Gemini) - Scheduled Task Runs Twice.
Q: Can I backup a single portal on my DNN Instance and restore it in other already running DNN Instance?
A: Not at this time. However, you can backup your DNN instance, restore it (as a new ‘cloned’ instance) and delete the portals you do not want to keep. What it is not possible at this time is “insert” a restored portal into another already running DNN instance.
Q: Can I backup a DNN version x.x.x and restore it in a DNN version y.y.y?
A: DNNBackup is not a DNN upgrade tool. To upgrade DotNetNuke, use any of the standard and recommended methods available to upgrade a DotNetNuke site. However, DNNBackup is very valuable to get a snapshot of your site before trying an upgrade (to be able to rollback) or to clone your site and test the upgrade somewhere else (i.e. a development or test “localhost” site – no license key required –).
Please find more FAQ and troubleshooting information in the module's documentation.
Licensing / Editions
| |
FREE Edition |
Single License |
Enterprise Subscription |
| Private Assembly |
Yes |
Yes |
Yes |
| VB.Net Source Code |
No |
not included / can be requested |
not included / can be requested |
Upgrade Policy
Within the maintenance period (which starts on the purchase date) you can download any latest release and upgrade your module for free. |
Always available |
6 months |
12 months |
| Installation License |
Unlimited 'localhost' installations |
Perpetual key valid for one production DNN installation.
Unlimited 'localhost' installations. |
Unlimited DNN installations (universal key
valid for any domain) for one year.
- It includes all the module's updates
within the licensed year.
- Once it expires, it can be renewed (50% discount)
or can be requested (no charge) to be turned into
a perpetual single license key (for one domain of the owner's choice).
|
| Redistribution |
Not permitted |
Not permitted |
Not permitted |