DNNBackup provides full backup and restore of any DotNetNuke web portal (whole DNN instances). The portal/database can be local or remote - including shared servers like GoDaddy, WebHost4Life and Discount ASP. The backup can include all web files and folders (\portals, \bin, \desktopmodules, web.config, etc.) and the database. Any size of database is supported along with most field types (including BLOB columns), relations, procedures and other database objects. The database is scripted as standard, commented and readable .SQL files. The restore can be made back to the source server or to a new destination.
If your database and web server are on the same physical machine, DNNBackup also provides native SQL Server backup and restore functionality.
DNNBackup is perfect for moving DNN portals from your local development machine to a deployment server, from a remote server to another remote server or for archival purposes. Power users can customize options. For example, backups can be scheduled and individual tables and fields can be customized information (e.g. insert a different module or portal id).
This Backup and Restore DotNetNuke module will work on ANY ISP.
DNNBackup is the evolution of BackupNative and BackupScript modules.
It’s not just a merge. It’s a complete rewrite with lots of improvements and new functionality.
F.A.Q
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 –).
See more FAQ on the module's documentation.