It has been a while since I've seen the WH4L interface, but the file manager does give you the ability to "zip" a directory. You'd would want to "zip" your DNn directory and use FTP to retrieve this file.

For SQL, using WH4L's SQL manager (I think that's what they call it), you can set up a backup plan. Follow the instructions. At some point it will ask you to create another FTP account on the SQL server. There you can download your DB backup.

As far as restore [say local], you'd create an IIS directory, unzip your DNN files there. Create a SQL DB (same name) and the User Account for the DB on your local SQL Server. Make a backup of the blank local DB. Now, unzip your WH4L DB backup into the same directory overwritting the blank backup. Now in SQL Manager, restore the DB (forcing an overwrite). Now the last thing to do is reassociate the DB user as it is orphaned. You can do this in Query Analyzer or SQL Manager Studio by running this query:

--Resolve an orphaned user

USE YourDB;
GO
sp_change_users_login @Action='update_one', @UserNamePattern='YourDBUserAcct', @LoginName='YourDBUserAcct';
GO

Hope this helps...

---

You might also want to check some 3rd party modules on Snowcovered.
Antony

Thanks Ed, but I assumed (which we all know is a bad practice) that the site came from the development server it was being sync'd back to, therefore the "local" alias would have already been entered....but my bad for assuming.

---