Evotiva - DNNBackup Module for DNN

Transcription

1 Evotiva - DNNBackup Module for DNN Page 1 of 53

2 Table of Contents Introduction... 4 Major highlights... 4 Key Features... 5 General Features... 5 Backup Features... 6 Restore Features... 7 About Evotiva backup solutions... 8 Release Notes... 9 Product Roadmap... 9 Product Editions... 9 System Requirements... 9 Installation... 9 Getting the module (module download)... 9 Installing the module (to perform backups) Hiding the module from the control panel Installing the module (to perform a restore from scratch) License Key Auto-install Configuration Database Backup Settings Native database backup method Requirements to be able to perform a native database backup DACPAC database backup method Script database backup method Files Backup Settings Offsite Backup Settings General Settings Global Options Notification Options Schedule Settings Schedule runner Editing a scheduled job About database objects backup methods Native SQL Server Backup Dacpac Database Objects Script Database Objects Save DataProvider Files Performing backup operations Manual backups Scheduled backups Configuring scheduled backups in two easy steps Schedule Runner Scheduled Job Main settings Database and Files backup schedule settings Scheduled job Database backup preferences Scheduled job Files backup preferences Scheduled Job History log Performing restore operations About the backup files name Page 2 of 53

3 Launching the Restore Wizard from the web site Launching the Restore Wizard stand-alone Advanced Options Run in Background Restore Priority Tables data groups Return Url How to get a clone of your web site Get a full backup of your source site Restoring the full backup on a different site/server Stage 1/3 - Restoring the Database Stage 2/3 Update the main Portal Alias Stage 3/3 - Restoring the Files Frequently Asked Questions Troubleshooting Support or General Questions Page 3 of 53

4 Introduction DNNBackup provides full backup and restore of any DNN (formerly DotNetNuke) Installation (complete instances). The restore can be made back to the source server or to a new destination. DNNBackup is perfect for moving DNN installations from your local development machine to a deployment server, from a remote server to another remote server or for archival purposes. Power users are free to customize many options. This Backup and Restore DNN module will work on ANY ISP, including shared servers like GoDaddy, WebHost4Life, Discount ASP and PowerDNN. DNNBackup is the evolution of BackupNative and BackupScript modules. Major highlights Ideal solution for website cloning, copy, move or archival. Our backup technologies are always evolving, and have been tested by hundreds of happy users since 2005! Check our reviews. Easy to use: There is no need for the user to configure any setting. The module is auto-configured with the optimal settings for the current hosting environment. Advanced users can customize what, when and where to backup. This is the first DNN Backup module capable of producing standard easy to read SQL scripts. Offsite backups: backups can be automatically saved to remote locations like a FTP server, Amazon S3, Rackspace CouldFiles and/or Dropbox. Evotiva DNNBackup can restore your site from scratch. This module does NOT depend on SMO or any other external component. It provides a wide range of backup options, adapted to all hosting environments. E.g., regarding the database backup, it can use the standard SQL Server (native) backup engine, the standard SQL Server DACPAC backup (based on SQL Server s APIs), the SQL Server's SMO interface, or it can use the module's own (TSQL) backup engine. Multiple schedules: advanced users can configure different scheduled jobs with different frequencies. Tested on most popular hosting providers including shared servers like GoDaddy, WebHost4Life, Discount ASP and PowerDNN. Tested on Medium Trust hosting environments. It still supports source DNN running SQL Server 2000 (up to the latest SQL Server 2005, 2008, and 2012 versions). Secure backup and restore operations: user credentials are verified before allowing any operation, password protected backup files. Optionally; you can choose Page 4 of 53

5 the folder name and location (even a protected folder, outside the web site root) where to store the backup files, and you can also choose how the backup files will be named. Key Features General Features Ideal solution for website cloning, copy, move or archival. Free fully functional for localhost domain, no license required. Free SQL Server native backups, no license key is required. Free complete portal files backups, no license key is required. True Full site backup and restore: database (structure + data) plus all files and folders on the site (including \portals, \bin, \desktopmodules, web.config file, etc.). Independency: You can create, backup and restore your site without any intervention from you host provider. Fast and Efficient: It can succeed even in hosting environments where the CPU and Memory are severely restricted. You can fine tune it to perform faster or slower, depending on your ISP and server limitations. Freedom: You can choose when you want to perform a backup, not your hosting provider. Note: some hosting vendors provide backup solutions but allow you only limited backups per day or week. It supports ANY ISP (tested on most popular hosting providers including shared servers like GoDaddy, WebHost4Life, Discount ASP and PowerDNN) Medium Trust Security Context support: The module can work in medium trust (most shared hostings are configured this way). Database Support: All SQL Server versions and editions are supported. From SQL Server 2000 to SQL Server 2016 (including the Express and Azure editions). More than backup/restore: useful as a table's data import/export tool, and among other functions, the module includes tools to help you understand your files and database tables size, and validate your database structure. Delegation: You can delegate to not-host users the backup task (including the scheduled backups monitoring) to any user with proper permissions on the page where the module was added. In addition, not FTP download access is required. All files can be downloaded from the module's "Browser". Page 5 of 53

6 Latest backups: Easy access and monitoring of the latest performed backups. The information (including download links) is available straight in the module's home page. Offsite backups: The module can automatically copy the backup files to an external FTP server and/or Amazon S3 and/or Rackspace CloudFiles and/or Dropbox. Regular users are welcome: In most cases, you don't have to be a tech geek or DNN guru to be able to clone your DNN site. The Restore Wizard guides you over the needed steps to get your clone up and running. You don't have to choose between power and simplicity. You can have both. Easy to use: there is no need for the user to configure any setting. The module is auto-configured with the most convenient settings for the current hosting environment. Advanced users can customize what, when and where to backup. Secure backup and restore operations: user credentials are verified before allowing any operation, password protected backup files. Optionally; you can choose the folder name and location (even a protected folder, outside the web site root) where to store the backup files, and you can also choose how the backup files will be named. Module Update Notification: There is no need for you to remember to check our site for new version availability. If you want, the module itself can notify you if there is a newer DNNBackup version available for download. Fine tuning: The module allows you to customize advanced settings, like the compression level, memory buffers sizes and the maximum file size for the generated script files. If it is desired or needed, by these settings you can make the backup process perform faster or with a reduced server footprint (useful for some weak or restrictive Hosting Providers). Backup Folder Browser: DNN File Manager like dialog, where you can handle all files found on the configured backup folder. Tools: It includes tools to help you understand which database tables are getting too heavy, or which files in your portal are too big. Backup Features SQL Server Native backup and restore: When available in your hosting environment, native backup and restore operations are supported by the module. Page 6 of 53

7 Database Maintenance: Along with the backup operation, you can configure the site to perform some routinely/healthy operations, like truncate the DNN Event Log or shrink the database (e.g. if you need to save hosting space). Scheduled backups: You can configure the module to perform scheduled backups. You don t need any administrative right to configure your scheduled task options or see the scheduled task's history. All the information you need is available on module's scheduler configuration page. Multiple schedules: You can define different, and as many scheduled backups as you want. E.g., you can define a daily backup of the data that changes more often and a monthly backup for more static data. You can also create a schedule to copy a single table's data or a set of portal folders, or a job just to clear the DNN Event log or shrink the database, etc. Offsite backups: The module can automatically copy the backup files to an external FTP server and/or Amazon S3 and/or Rackspace CloudFiles and/or Dropbox. The module can be configured to delete the local file once it was uploaded. Notifications: Notification s (w/customizable templates) for backup operations. Huge Backup Files The module supports the Zip64 format, which means almost unlimited size and capacity for the backup ZIP files. Secured backups: you can setup the module to password-protect the generated backup ZIP files. Retention Policy: You can configure automatic deletion for old backup files. Optionally, date & time can be appended to each backup file name (each backup operation will generate a different backup file). Inclusions/Exclusions: You can choose which tables, files and folders you want to include or exclude from the backup. You can even select 'external' folders (folders outside the web site's root) to be included in the portal files' backup. Wildcards for folders exclusion rules are supported. Human friendly There is no need to read cryptic XML or CSV files. DNNBackup writes standard human readable and updateable.sql query files, which you can edit, modify and even manually run! Any database size is fully supported. Restore Features Restore Pack: DNNBackup can restore/rebuild a site from scratch. No running DNN is required to rebuild a site. You just have to unzip the 'Restore Pack' in your blank/empty web site and follow the Restore Wizard. Page 7 of 53

8 Restore Pack Loader: It is a tiny (10 Kb) web application you can install (unzipping it in your web's root folder, and browsing to the /RestoreWizardLoader.aspx page) in your destination sever instead of the complete 'Restore Pack'. Restore Wizard: A user-friendly wizard, which guides you through all the steps needed to restore or clone your saved DNN instance (database and files). It is a standalone application. You don't need a running DNN site to restore a backup. SQL Query Tool: Handy tool included in the Restore Wizard, from which you can execute SQL statements against the database. It supports {directives} and /* comments */ same as the built-in DNN Host SQL utility. Safe Settings: DNNBackup can set Host Settings, refresh the WebServers table, reconfigure the site's SSL settings, or update the main Portal Alias for you. Table s data filter: You can set a filter to restore just some (or one) table s data. Power users can customize the generated backup file and e.g. be able to restore individual tables with customized information. 'Object Qualifier' customization: When restoring, you can replace it (even leave it blank). There is no need to keep the original ObjectQualifier. SQL Server version downgrade: When restoring a 'script' database backup, it does not matter the source SQL Server's version. You can restore in SQL Server 2005 a site that is running in SQL Server 2008, or you can restore in SQL Server 2005/2008 a source site running in SQL Server 2008 R2. Portal Files: all the portal files and folders are restored to their original locations. When cloning a site, the web.config file is automatically updated to match your new database connection. About Evotiva backup solutions Since 2005, our DNN backup solutions are trusted and tested by thousands of users worldwide. Check out our rank and reviews (DNNBackup, BackupNative & BackupScript). Superb support. Simple and flexible licensing installation and policy. Our previous BackupScript module was the first and only backup module reviewed by DNN Corp. And more. Please try it and check by yourself. Page 8 of 53

9 Release Notes Please see Product Roadmap Please see Product Editions Please see System Requirements DNNBackup requires DotNetNuke version or later (including all DNN 5, DNN 6 and DNN 7 versions). The database can be SQL Server 2000 or later (including all editions of SQL Server 2005, 2008 and 2012). SQL Azure is also supported. Amazon S3, Rackspace CloudFiles and Dropbox integration will work even in a mediumtrust hosting environment (with 'WebPermission' enabled). FTP operations requires the web site to operate in Full-Trust security context (set by the hosting environment). Installation Getting the module (module download) The module is available for download at our web site. Please visit our downloads page ( to get the module. You should download both the DNN module, which you will install in your DNN portal to perform backup and eventually restore operations, and also the Restore Pack which will allow you to perform restore operation on a blank/empty web site, where DNN is not running (or it was running, but it is no longer operational). VERY IMPORTANT - WHEN UPGRADING THE MODULE FROM A PREVIOUS VERSION Page 9 of 53

10 Before upgrading the module to a newer version, please make sure the service period of your license has not run out. Trying to upgrade with a version released after this date will invalidate your license key. Be sure to verify in Configuration > License Key and Details, your "Maintenance Expiration Date" BEFORE upgrading the module. If this date is previous to the date of the release you would like to install, once installed the module will NOT work. If you have a Perpetual key, it will work forever, it does not expire. What the "Maintenance Expiration Date" rule is the period in which you can get free upgrades. If you have installed by mistake a new version invalid for your "Maintenance Expiration Date", uninstall the module and install an older version suitable for your service period (stated by the "Maintenance Expiration Date"). Note: If your current version of DNNBackup is previous to 4.3.2, you must uninstall the previous version before installing this one, because the module's name was changed to avoid conflicts with UrlScan (an IIS Server add-on) on some servers. Installing the module (to perform backups) To install this module, you just have to follow standard DNN module installation procedure: From Host > Extensions > Install Extension Wizard. Remember that you must login to your web site as a Host user to have access to this functionality. The installer will create a Host > DNN Backup page with an instance of the module in it. IMPORTANT: For security reasons, add this module just to a protected (not public) page, accessible only to the proper DNN security roles and/or users. Please find help/demo videos here: Hiding the module from the control panel For security reasons, once you added the module to a page, you may want to prevent the module to be added to another page. To accomplish this, you can use the premium feature, which simply removes the module from the drop down list without removing it from any page. Check the DotNetNuke documentation for more information about Premium Modules. Installing the module (to perform a restore from scratch) In this case, you ll use the Restore Pack, not the DNN module. Please refer to the Performing Restore Operations > Launching the Restore Wizard stand-alone section. Page 10 of 53

11 License Key The module includes a built-in license key enabling complete functionality on any dnndev.me, localhost or *.local sites (e.g. or and some limited functionality on any other site. Once you have purchased a license key suitable for your web site s address, please use the Request License Assistance link available on the Configuration > License Key and Details page to request your purchased license key. Once you get the key from us, install your license by visiting the Configuration > License Key and Details page. Select your license text file from your local machine, and click on the "Upload and Update" link. Note: - If your purchase was at the DNN Store, the download available for your purchase is a temporary license key suitable for any web site. Therefore, you do not have to wait for us to activate the full functionality for the module. - If your purchase was at evotiva.com, a temporary key has been ed to you (to the address you've utilized to make the purchase at PayPal). Therefore, you do not have to wait for us to activate the module. Auto-install The license key can be automatically installed. You can rename you key file as Evotiva.DNNBackup.LicenseKey.resources, and upload it to /portals/_default or /DesktopModules/Evotiva-DNNBackup. It will be automatically installed (and the file deleted) when browsing to the module s home page, when running a manual or scheduled backup, or when running the restore wizard in standalone mode. Page 11 of 53

12 Configuration By default a full backup (database and files) is configured. There is no need for you to change any setting. The module will automatically configure itself with the optimal settings for the current hosting environment. The module will not allow you to enable settings that it guesses will not work in the current environment. E.g. ftp transfer when not running in a Full-Trust hosting environment. We have designed the module to be as much self-explanatory as possible. Navigate through the different configuration pages and check for each setting s built-in help information to learn about each one. Page 12 of 53

13 Database Backup Settings Native database backup method Page 13 of 53

14 Requirements to be able to perform a native database backup To perform a native backup from the module, these conditions must be all true: a) Web and database servers must be the same physical machine. b) The database user (in the connection string) needs database permissions to perform a 'backup database' t-sql command. c) The user running the sql server service need file system permissions on the configured backup folder. DACPAC database backup method NOTE: It is important to run it at least once the Database schema analysis tool, to verify your database (especially when relying on DACPAC backups). Page 14 of 53

15 Script database backup method Page 15 of 53

16 Files Backup Settings Page 16 of 53

17 Offsite Backup Settings You can define many offsite locations at the same time. The order in which they will run is the same as their appears in this screen. To save local web site space, you can enable Delete local file on the last offsite operation to be run. Page 17 of 53

18 Page 18 of 53

19 Page 19 of 53

20 General Settings Global Options IMPORTANT: It is advised to password-protect your backup files. Otherwise, anyone with access to the files will be able to get sensitive information from them. Page 20 of 53

21 Notification Options Page 21 of 53

22 Schedule Settings Schedule runner Page 22 of 53

23 Editing a scheduled job The common schedule settings are edited in this page. All the specific settings for database and files backups are set on each specific configuration page. You can choose whatever combination of settings you want in as many schedules as you want. About database objects backup methods There are three methods to get the database structure: 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 Dacpac Database Objects When native backups are not available, on most cases this is the preferred method. It is based on standard SQL Server APIs, and includes the database structure and its data. The result is very similar to what SQL Server creates as a backup of an Azure database. NOTE: It is important to run it at least once the Database schema analysis tool, to verify your database (especially when relying on DACPAC backups). 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. Page 23 of 53

24 - this will work on any ISP, including GoDaddy Note: at this time, SQL Server assemblies are not supported by this backup method 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. However you can recreate any missing object by means of the Script Database Objects setting. By the way, this method enables changing the ObjectQualifier. If in the source server was defined e.g. 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 Note: if the database holds object not being created by SqlDataProvider defintions, they will not be recreated on the destination database. Performing backup operations Manual backups On the module s main page, there is available a Perform Backup button. Clicking on it will trigger the backup process. It will use the currently configured backup settings. Page 24 of 53

25 If you enable the Run in Background checkbox, the backup will be run as a scheduled task (called Background Manual Backup ), which will be launched immediately. This feature needs the Schedule Runner enabled. Otherwise, the backup will not run. On the Configuration > Schedule Settings page you can review if the backup was completed and its status. If notifications are enabled, you ll get the expected . You can select to trigger the database and/or portal files backup, and it the feature is available in your hosting environment, you can also enable some of the offsite transfer options (FTP and/or Amazon S3 and/or Rackspace CloudFiles). You will see a visual clue about the database method (Native or Script) and scope of the backup (Complete or Partial). Once the backup is completed, you will have direct access to the latest (local) backup files from the same main page: Clicking on the download icon, will trigger the file downloading. In addition, you will get a notification , in case this feature was enabled in the General Settings page. Page 25 of 53

26 Scheduled backups DNNBackup allows you to schedule different kind of operations. E.g. you can schedule a daily backup for the data changing more often (like the database and the \Portals root) and a monthly backup for more static data (like the other portal folders). The backup will run based on the configured settings and will notify you the results by , in case notifications were enabled. Please find help/demo videos here: Configuring scheduled backups in two easy steps 1. Configure the schedule runner: Depending on your needs, having it running once a day could be fine. If you want the backup to run a specific time, or you have many scheduled backups configured to run at different times, you better configure the schedule runner to run e.g. every 1 hour or so. 2. Create your schedule(s) backups: a) On the 'Configuration > Database Backup Settings' page, click on the Add new schedule' link found in the 'Scheduled Backups' section to create and configure a new scheduled backup. b) If you want the backup to perform also a files backup, on the 'Configuration > Files Backup Settings' page, click on the edit pencil image next to the just created scheduled job and edit its file-related settings. Note: You can create schedule(s) for just database, just files or both, with any combination of settings for each one, and also defining independent Offsite backup options for each one. Ready! Important: Do no create many backup jobs that might run simultaneously or too close one to the other. DNNBackup will not allow it and in the job s history you will read backup skipped. You can disable this functionality or change this behavior by means of the Backup Run Threshold setting found on the module s Configuration > General Settings. Page 26 of 53

27 Schedule Runner This is the standard DNN Scheduler configuration. On each iteration, it will review all DNNBackup schedule jobs and run them according to their own configured schedule. For the backups to be run, the schedule running must be enabled. Page 27 of 53

28 Scheduled Job Main settings For each schedule, you can configure whether to backup the database and/or files and which offsite operation(s) to perform. You can define a preferred start time for the job. E.g. you may want the job to run at night, when the site is being less accessed. Note: a DNN Scheduled task is not guaranteed to be run, and you cannot set a specific time for it. Check the DotNetNuke documentation for more information. However, if you have the Schedule Runner configured to run every few hours, your site is being kept alive, and you have set a preferred start time for the schedule job, chances are very good for the job to run according to your preferences. Page 28 of 53

29 Database and Files backup schedule settings From the regular Configuration > Database Backup Settings and Configuration > Files Backup Settings page pages, you can configure your preferences for a specific scheduled job. All settings can be customized. E.g. you can define different database file names, which tables and portal folders include/exclude, etc. Page 29 of 53

30 Scheduled job Database backup preferences Page 30 of 53

31 Page 31 of 53

32 Scheduled job Files backup preferences Page 32 of 53

33 Page 33 of 53

34 Scheduled Job History log For each scheduled job, you can see its schedule history: Page 34 of 53

35 Performing restore operations You can restore on the already running site (the same where the backup was created) or could be an empty web site (no DNN and blank database). Please find help/demo videos here: About the backup files name The module will identify the backup files based on its name. The backup process creates the proper names for the backup files. In case you manually changed a file name, this is the naming convention for the DNN Backup files: *_native.bak = Decompressed Native database backup *_Native.bak.zip = Compressed Native database backup *_files.zip = Files backup *_script.sql.zip = Script database backup Launching the Restore Wizard from the web site On the module s main page, there is available a Launch Restore button. Clicking on it will trigger the Restore Wizard. Following its steps, you can restore your web site from any available backup file. Page 35 of 53

36 Launching the Restore Wizard stand-alone Download the Restore Pack from Then unzip and upload it to the (blank) web site s root. Browse to Alternatively, use the tiny Restore Pack Loader to install the Restore Pack (stand-alone Restore Wizard) for you. 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: or Note: The restore pack includes a 'This web site is undergoing scheduled maintenance' default.aspx page for the web site's root and the web site will be set on off line mode while a restore is being performed. The Restore Wizard will guide you thru the steps needed to perform the chosen operation. It should allow you to perform only operations it thinks will be able to accomplish. Upload the backup files to be restored in the just created (included in the restore pack) /backup folder. Page 36 of 53

37 Advanced Options You can call the Restore Wizard with some special options. Run in Background Note: This is valid just for manual backups. Restore Priority or 1 or 2; where 0=normal, 1=slow, 2=slowest Tables data groups or From all the Ins_... scripts included in the backup file, the restore will just process the selected number of scripts. Let s say you have a very problematic hosting, who is killing your application pool too often, and let s say you would like to restore a backup which includes more than 900 scripts for inserting data into tables. By means of these settings, you can process them by groups, fooling the hostile hosting provider. Page 37 of 53

38 You can combine these settings. Sample: This will make the restore process to run slowly, and it will just restore the first 100 Ins_ script files. Return Url aaaaaaaaaaaaaaaa is an encoded URL. Once the manual (and no background) backup is successfully completed, the page will be redirected to this URL. Our DNNUpgrade module takes advantage of this feature. How to get a clone of your web site Get a full backup of your source site A full backup of your site is a full database backup + a full files backup. A full database backup is: A native database backup or A script database backup including: - Save DataProvider Files: Enabled - Script Database Objects: Enabled - Script (backup) Tables' Data: Enabled - Tables List: Backup data for ALL except the assigned tables - No table in the Assigned list (or just assigned the tables configured by the 'Assign known not-critical tables link in the database settings page). A full files backup is: A files backup including: - Include web.config file: Enabled - Include 'Host' folder: Enabled - Include \bin folder: Enabled - Include Modules folder: Enabled - Include \App_Data folder: Enabled - Include other folders: Enabled - Exclude Foldes List: typically empty, unless you know what you are doing Restoring the full backup on a different site/server Page 38 of 53

39 NOTE: you can clone/restore your site into an empty web site (empty database and web root). There is no need to install a DNN before running the Restore Wizard (loaded from the Restore Pack ). The same prerequisites as for DotNetNuke applies. You need a SQL Server database already created and with known credentials, and you need a properly configured empty (or not) web site with the proper file system permissions set. You can see the standard DotNetNuke documentation for more information about this matter. Stage 1/3 - Restoring the Database On the Restore Wizard, choose the Database Restore (an Evotiva.DNNBackup 'Native' or 'Script' Database backup) operation. Follow the wizard steps. It will guide you. You will be presented with a list of suitable files available for restoring (native compressed, native decompressed or script compressed backups). Page 39 of 53

40 IMPORTANT: If the wizard guesses that native restores and not suitable for your current environment it will not make them visible in the Select Database Restore File page. Page 40 of 53

41 Page 41 of 53

42 You can select a file from the local file system (on the web server s backup folder) or choose and off-site backup file, which will be downloaded to the web server and made available as a local backup file. If you are performing a Script backup restoring, on the script restore settings page, you should select Apply Data Providers or Create Database Objects AND Restore Table s Data. The Restore Wizard will setup these default settings for you. It will also set the Object Qualifier found in the source database backup file. Page 42 of 53

43 If you are performing a Native backup restoring, on the native restore settings page, typically you can leave No Recovery Restore unchecked and accept the proposed Auxiliary Database. If an error is thrown when attempting the restore, try a different Auxiliary Database. If still fails could be that you don t have permissions to perform a restore in the current hosting environment. The User ID and Password on this form are regarding the auxiliary database. These credentials could be different to the ones provided to connect to the to-be-restored database. Page 43 of 53

44 Page 44 of 53

45 Once the process is completed, it will end with a message like this: Stage 2/3 Update the main Portal Alias Click on Back to the Restore Wizard link, and accept the suggested default Operation: Set a proper main Portal Alias and/or set safe Host Settings. Page 45 of 53

46 You will get the Main Portal Alias and Safe Host Settings page: Page 46 of 53

47 Page 47 of 53

48 Use the Update the Portal Alias link to update the database Portal Alias for currently running web site. If desired and/or needed, use the Apply Safe Host Settings link to reset some Host Settings. The Disable SSL is useful when you are cloning you site in a server where there is no SSL certificate installed (E.g. your local machine). Click the Next button when ready. You will get the SQL Query Utility page. In this page, advanced users can perform some queries against the database or perform additional updates to it (e.g. replace additional Portal Alias ). Page 48 of 53

49 Stage 3/3 - Restoring the Files Click on the Restart Wizard and accept the new default operation: Files Restore (an Evotiva.DNNBackup 'Files' backup). Once you choose a backup file to restore and click on the Execute Operation, all the files will be restored to their original location (NOTE: current files will be overwritten) and the restored web.config file will be automatically reconfigured (connection string, databaseowner and objectqualifier) for the new database. Page 49 of 53

50 Page 50 of 53

51 Page 51 of 53

52 Frequently Asked Questions Q: Should I perform Native or Script backups? A: It depends on what do you want to do with the backup. If you want to clone your site as it is, Native backups are always the best option. 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. Note: this method will not work at GoDaddy. If you are not sure about native restore capability on the target server, then choose to perform a Script backup. Q: Can I backup a single portal on my DNN Instance and restore it in other already running (or just installed) 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: If you backup version x.x.x, you will restore version x.x.x. Q: Does this module will save my child portals? A: Yes. The module handles the DNN Instance as a whole. Therefore, all portals (parent and/or child) will be saved and restored. Q: How can I clone my site with this module? A: See How to get a clone of your web site in this document. Q: Can I use DNNBackup to move a site from one ISP to another? A: Yes, you can. Q: Can I use DNNBackup to move a site from development to production? A: Yes, you can. Q: Can I use DNNBackup to upgrade my DNN installation? Page 52 of 53

53 A: Please see our DNNUpgrade module: Troubleshooting Support or General Questions Please us to or use the form available at our web site ( Page 53 of 53