Hi togehter first of all: 1. after you finished installing an win2k you should create a repairdisk. there you have the files you need. if you change some important system files, you'll be prompted to refresh your repaidisk. 2. boot.ini is not located in adsm.sys. look at the schedlog. there you will find the boot.ini. (with TSM V4.1.2.12) 15-03-2001 22:02:27 Preparing System Object -> System VolumeNormal File--> 185 \\servername\c$\boot.ini [Sent] 3. config.sys is not a needed file to startup win2k. this is only for old an not win2k certified applications. 4. multiple copies of system objects (files) are not supported by ibm (or ms?). may in the next release or version? ok,ok, i never restored a win2k with tsm, but it's in pending state on my todo-list. a restore with nt backup is easy, problem free. have a nice weekend cd -----Ursprüngliche Nachricht----- Von: Rushforth, Tim [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 22. März 2001 22:58 An: [EMAIL PROTECTED] Betreff: Re: System Objects for Windows NT Backup of System State does not include boot.ini, it does include ntldr and ntdetect.com. I don't think it contains config.sys. TSM DOES NOT backup boot.ini as a regular file. It does not back up any files that are included as part of the System Object. Renaming the System Object on TSM after the backup does work - I've tested this out. This is documented in the TSM with W2K redpiece. One reason to use the NT backup method is that it gives you the ability to archive the system state which you cannot do at all with TSM. Tim Rushforth City of Winnipeg -----Original Message----- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 22, 2001 3:45 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, The NT systemstate contains most (but not all of the same things that are backed up by the TSM System Object), so in that respect it captures more than whats held in ADMS.SYS I know that the System Files component of the System State contains many of the O.S related files for Windows 2000. This includes files that are held in the WINNT directory. However, I'm not sure if the System Files component includes the boot files that sit in the root for the drive (boot.ini etc). We backup the C drive anyway so even if the boot.ini, config.sys etc aren't captured as part of the Windows 2000 System State backup, they get included in the file system backups. I know that it's likely that we're 'double-dipping' some files but it's better than not getting them at all : -). Our typical backup schedule works as follows: 1. Use the Windows 2000 Scheduler to trigger NTbackup to backup the System State to a disk file. On a system without Active Directory the file size isaorund 300mb. For a domain controller with would obviousl be bigger depending upon the size of your AD. 2. After a reasonable time window (to allow NTbackup to do it's stuff), do a TSM backup of C drive , System Object plus any other drives you need. The file created as by NTbackup is then backed up at this point. Other than using NTbackup the only other way that I thought that you could get around this problem would be to rename the System Object filespace on the TSM server to correspond with the backup date (or someother unique name). That way it would always remain active. Then if you need to restore it, you just need to reamne it again before starting the recvoery process. However, I haven't had anytime to reseach this, so I don;t know how 'doable' this is. The Ntbackup method seemed to be the quicked way to acheive a result, although probably not the cleanest. Andrew Pearce BHP Server Engineering, CSC Australia PO Box 261, Warrawong, NSW 2502 email: [EMAIL PROTECTED] Tel: 0242 75 7135 Fax: 0242 75 7923 "Collins, Brenda" <Brenda.Collins@WEST To: [EMAIL PROTECTED] GROUP.COM> cc: Sent by: "ADSM: Dist Subject: Re: System Objects for Windows Stor Manager" <[EMAIL PROTECTED] U> 23/03/2001 01:53 AM Please respond to "ADSM: Dist Stor Manager" Andrew, Thank you for the feedback. I looked at this once and I believe it does the same thing the adsm.sys file does in terms of what it captures. What do you do about the boot.ini, config.sys, ntldr, etc. that you might want multiple copies of? They don't get put into the system objects stored in adsm.sys, are they kept with the NT backup? Brenda -----Original Message----- From: Andrew Pearce [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:43 PM To: [EMAIL PROTECTED] Subject: Re: System Objects for Windows Brenda, We schedule NTbackup to backup the Windows 2000 System State to disk and then pick this up as a file via TSM. Not particularly elegant, but as a short term fix it meets our requirements. You obviuosly need to be familar with a recovery process that incorparates NTbackup to do this. I've heard that the inactive system objects issue may be addressed in the next release of the client (4.2) - certainly hope so - can anyone confirm this? Andrew Pearce email: [EMAIL PROTECTED] "Collins, Brenda" <Brenda.Collins@WEST To: [EMAIL PROTECTED] GROUP.COM> cc: Sent by: "ADSM: Dist Subject: System Objects for Windows Stor Manager" <[EMAIL PROTECTED] U> 20/03/2001 03:51 AM Please respond to "ADSM: Dist Stor Manager" Has anyone implemented a solution they would be willing to share that will keep copies of inactive system objects? Brenda Collins, Storage Solutions Group Phone: 651-848-5808 Email: [EMAIL PROTECTED] Disclaimer: "The views, opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by West Group."
