You can run ntbackup, and backup the system state to a file.
You can then archive the file. 


Do you really need the system state though.
If you're talking long term, your chances of finding matching
hardware to do a bare metal restore is slim. In most cases
you can build a new server, reinstall the apps, and restore
the data. Just remember to keep installable copies of your 
applications as long as you keep the archives.


-----Original Message-----
From: TSM [mailto:tsm AT PROFI-AG DOT DE]
Sent: Wednesday, March 24, 2004 8:00 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: need help!! long time archiving and storing corresponding
systemstatus


hello,

the environment is w2k and nt client nodes (over 200) and in near future
w2003.


short description of my problem:
i have to archive data for long time retention, with the possibility to
recover servers completely out of this archived data.


my first joice is to archive this data, but there are some serious
problems:

-  the data will be useless without storing the corresponding systemstatus
data (shares)
-  tsm does not support archiving of systemstatus, i have to backup
systemstatus instead


so i have on the one hand my archives with retentions periods (weekly,
monthly, quarterly and yearly) and on the other hand
systemstatus backups with versioning.

backing up systemstatus and hold 1000 versions for every of our 200 servers
in tsm is not the solution we think of.

please help, if you have experiences or suggestions.


with best regards

stefan savoric