DNN based sites consist of 2 components:

• the file structure which contains the code which is the "framework" for running the site.
• the database which contains settings, data, and content for the site.

When you add modules, you may add both files to the framework, as well as add or modify database table structure and data.  As a result, it's important that when you back up a DNN based site, that you get a "point in time" snapshot of both files and database (i.e., both done at the same time).

Because our file system backup and our database backup solutions run asynchronously, they will not necessarily be captured at the same time.  As such, if you need a backup of your DNN site, it's strongly recommended that you submit a support request for a complete backup to be made of your DNN site.  Your request should include verbiage similar to the following:

Please create a complete backup of my DNN based site, including a ZIP of my site files, and a FULL backup of my DNN site database: (insert database name here).

With this request, our team will make these backups, and make them available for you in the PRIVATE folder of your FTProot.  You can then download these, and maintain a copy yourself.  YOU SHOULD NOT make any settings changes or add/remove/modify any modules/etc from the time we make this backup until we notify you it's complete.

It is STRONGLY recommended that you obtain a complete backup of your site in this fashion:

• if you intend to UPGRADE your DNN version... this will ensure you can roll back to where you were.
• if you intend to install MODULES which are of questionable stablility.
• if you have no local backup (your own copy on your own system) of your DNN based site.