in version 10.x almost all of the stuff (including maps, views, etc) is kept in database. So be sure to have a valid sql database backup.
A document which can give you a better picture of what you need is the following:
Even is a migration guide, by viewing the procedure you can be sure on what you are going to need in an unlike event of failure.
I just went through a server and database migration. This isn't a complete list but it is at least a partial of stuff I've found you may need to backup or be ready to restore by hand;
All files in the reports directory
Local Config-Archive (if you use this option, the database does keep some but may not have all your local files)
Custom device types
I also found a lot of these scheduled jobs show up in the Windows Task Scheduler. I believe the job files are the actual "what to do", while the Windows Task Scheduler is what fires it off at an appointed time. Definitely need the job file, but you'll need to backup the Tasks if you don't want to reschedule all of the jobs.
Be careful where you restore these files... If you have a different directory structure or drive you are restoring to , some of these files may reference directories that have changed. You can open the files and find the directories and replace them as needed.
Anything special or custom in your published website directory ... If you have a job that creates files left on the webserver, you may need to recreate the folders and modify IIS settings to re-allow them to be visible.