Re modules for backing up, take a look at BackupLite (http://gruposur.com.uy/Default.aspx?tabid=96). Essentially, it looks like this runs a database backup (or "dbdump" for old-school types), and puts this in a zip file you can download. It looks like the "Pro Edition" lets you also put parts of the file system, including the \portals and other directories, into a zip file. It also adds scheduling.

I haven't tested actually doing a restore, though. If it really works, this could be a good tool to help get back up and running after a catastrophic failure. Most disasters that I've seen, though, are more along the lines of someone messing up and deleting or changing the wrong thing. For something like that, I'd very much like the ability to restore just one portal.

I thought that a strategy for fixing a single portal would be to restore a database and file system backup to a temporary server, exporting a template (with content) for that portal, copying that template to the production server, and finally using this as the template to recreate the portal structure and content. However, it looks like this doesn't bring all content and module settings in correctly. I've actually seen this put content into the wrong portal!

I think this happens only with some modules. I don't know if this is a base dnn problem or a module problem?