I'd like to recommend this variation or extension of the backup procedure:

If your hosting account allows you to backup, create and restore the db then it's worth getting into a routine whereby you make a functioning duplicate of your site rather than just a set of backup files. Once you are used to carrying out the related tasks, you'll be a lot more confident about working on your site.

1. Make a new folder on the server - I like to add the target DNN version number to the root folder name e.g: Mynewsite-436
2. Set the necessary network_service = RWXD permissions for DNN on the new site folder.
3. Point a domain to the folder - I keep a spare domain just for this sort of thing and ensure that this domain is always listed as an alias in the site settings. Or redirect your original domain if you don't mind the temporary site outage.
4. Install FP extensions if you use Frontpage for managing the files.
5. Set the domain/folder to ASP.Net 2 if you're using DNN4
6. Transfer your site to the new folder via FTP or Frontpage. Your webhost might also copy the files over for you. Note: Rename the web.config before uploading so that the duplicate site is disabled.
7. Backup and then restore your database to a fresh blank db that has a new name.
8. Modify the web.config with the name of the new db and rename the file back to web.config
9. Fire up the new site in your browser - give it time to compile.

At this point you're running a perfect duplicate of your old site. You can now carry out the upgrade as detailed by the otehrs above. If everything works fine then you're all set. If it fails then it's no problem to revert to the old site - just redirect your domain back to it.

I've got into the habit of publishing (syncronising) my site locally as a backup with Frontpage and then syncing from the backup to a duplicate site on the server for testing modules or doing anything else drastic, such as testing an upgrade.

Regards,
Rob