If you are serious about disaster recovery planning, every site is different. I'd recommend engaging with a consultant. But here are the general steps assuming you use CMS 7 in an environment that has only one NS.
Database (settings, configurations, jobs, tasks, reports, etc)
Your database holds most of the information used by Altiris. Make sure your SQL database is backed up daily using an enterprise backup solution, and hosted or replicated off-site.
Software Library (software packages, images, files, and other resources)
Your software library holds whatever isn't in your database, so be sure that this location is backed up daily, or at least weekly.
Server
You should be backing up your server daily, at least weekly, using an enterprise backup solution that replicates the backups off-site.
Username and passwords (service accounts and the like)
You should have these stored in a password safe or other secure method which is backed up off-site using an enterprise backup solution.
Your restore would generally consist of these steps:
- Build a new server and configure it with exactly the same installed solutions and version levels (right down to Service Pack and hotfix levels)
- Configure it using a temporary database
- Go to Settings > All Settings > Notification Server Settings > Database Settings and point it to your backed up SQL database
- The restored database will have settings pointing to your restored Software Library (if you had to restore the Software Library to a new location, just update the settings).
Refer to this document:
http://www.symantec.com/business/support/index?page=content&id=HOWTO2927
And also to this document:
http://www.symantec.com/business/support/index?page=content&id=HOWTO3480
For best practices. They refer to Altiris 6, but I haven't seen any updates for Altiris 7.