Maintaining Your Site
You should take regular steps to regularly back up your site in case something happens to the computer on which your site is running.Listed below are common steps you should do whenever possible. As a rule of thumb, you should back up your site as you generate
Back Up Your Database
You can usually recreate all the content (images/themes/files) stored on your database. Your content is the lifeblood of your site and needs to be treated as such.
Note: If you receive a File in Use notification during your database backup, stop the IIS Website, then continue with the backup.
VistabDB and Access
To back up a VistaDB or Access database, all you need to do is download it. Using Graffiti's FileBrowser, you can do this from directly within Graffiti’s control panel.
- From the control panel, navigate to Site Options > Utilities > FileBrowser.
- From there navigate to your database file. The default location is App_Data > Graffiti.mdb.
- Select the file which takes you to a page with information about your file.
- On this page, select Download and the file will be saved locally.
MySQL & SQL Server
SQL Server has a built-in backup utility built in and hopefully your ISP site administrator has set it up to perform daily backups. However, you should still store a backup of your database on another computer. This is especially true when using shared hosting
because you may not know who is maintaining the server for you.
Back Up Custom Files
With folder generation enabled, Graffiti generates quite a few files for you. It usually generates a new file anytime you create a new category, post, or tag. While these files are very important to Graffiti, they do not need to be backed up since Graffiti
can easily regenerate them for you (Site Options > Utilities > Regenerate Site
The files you should be most concerned about are those you have customized, such theme .view files, theme css files; files you have uploaded, such as images, movies, and mp3 files; or configuration files (
config) you have changed.
However, the best solution is to make regular backups of your entire web directory and store them somewhere other than your web server.