I agree that both ways work. If you have a LOT of Win2K servers to back up, using ntbackup is arguably better because tsm system object backup creates 1800+ entries in the TSM DB for EACH backed up version of the system object. Lots of overhead, if you have lots of Win2K machines. Using ntbackup to a flat file, you get 1 entry in the TSM DB for each backup version.
-----Original Message----- From: Robertson, G Louis (BearingPoint) [mailto:[EMAIL PROTECTED] Sent: Thursday, February 26, 2004 10:34 AM To: [EMAIL PROTECTED] Subject: Re: Incremental backups Nicolas wrote: "3. What about backing up the system state of a windows 2000 server? Is it ok to perform "dsmc backup systemstate" or is better to use NTBackup utility and save the backup file on the disk and then backup that file with TSM." I use ntbackup to backup up the systemstate because I found in earlier versions of TSM (4.x) I had problems restoring with just the "dsmc backup systemstate". We have a preschedule task that does an ntbackup of the systemstate prior to our incremental backups. Here is the syntax I use: ntbackup backup systemstate /f "C:\Srvutils\Systemstate.bkf" /m copy Louis G Louis Robertson Senior Systems Analyst BearingPoint [EMAIL PROTECTED] Cell (717) 903-1324 Fax (717) 213-6101 **************************************************************************** ** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. **************************************************************************** **
