separate web and database backup
0 vote
Hello,
i would like to see a modification of the backup routine.
The web backup is an archive of the web root folder.
That content only changes when you update the site.
Only thing that changes between updates id the APP_Data sub folder with the logs, and maybe the App.config file?
So maybe this could be split in a backup of the "static" web content, and the "dynamic" configuration and logging.
An other problem is that the web backup is created in the system temp folder, and therefore inherits the permissions of that folder when it is moved to the specified backup location. That is a problem when a non privileged user needs to access or move the files.
It would also be nice to have different schedules to do a database backup more frequent than the web backup.
and maybe a pre / post script option to do things before or after the backup.
All Comments (1)
Hello,
Thank you for your request. You're right, the web root folder doesn't change much. We added that feature a long time ago as a basic tool to help customers without knowledge of backup. We could probably have different schedules for database and web backups; that part should be easy. However, users will need to know which web server backup fits with which database backup because versions could change between two database backups. Web server backups could be avoided if you save your encryption config file and your app settings files safely, so you could restore your system by installing the right version and applying your encryption file and your database settings (connection string).
I will keep your suggestion in mind if we could at least split the schedule between database and web server backups. We don't have a work plan for your other requests, but I will follow that thread to see if it could help other users who would like similar features.
Best regards,
François Dubois