ADSM-L

Re: [ADSM-L] TSM system state backups or NTBACKUP

2008-11-26 01:28:38
Subject: Re: [ADSM-L] TSM system state backups or NTBACKUP
From: גדעון בראון <GideonB AT COURT.GOV DOT IL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 26 Nov 2008 08:27:58 +0200
Hi,

We gave configured NTBACKUP with it's wizard to perform daily backups to local 
disks (d:\ntbackup).

TSM backup this directory during its daily backup routine.

So, we use both TSM system state backup and NTBACKUP.

Gidi

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Tim Brown
Sent: Tuesday, November 25, 2008 11:55 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM systemstate backups or NTBACKUP

How are you automating the NTbackup on your AD servers
The servers causing me issues are in fact AD servers.

Tim

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Zoltan Forray/AC/VCU
Sent: Tuesday, November 25, 2008 2:50 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM systemstate backups or NTBACKUP


We use it on hundreds of servers with no problems.  We have seen problems
caused by the infamous DRM registry key and VSS but most problems have
been fixed with newer clients and Windoz patches.

On our AD servers, we are using NTBACKUP because M$ says that is the
*ONLY* acceptible/sanctioned backup/restore utility but still backup the
rest of the system with TSM.




Tim Brown <tbrown AT CENHUD DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/25/2008 02:29 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
[ADSM-L] TSM systemstate backups or NTBACKUP






Is anyone using the Windows NTBACKUP to backup Windows
servers SYSTEMSTATE instead of relying on using TSM
to backup the system state.

I am always running into issues with some servers not able
to get a successfull SYSTEMSTATE backup via TSM

Latest clients have been Windows 2003 servers at 5.5.0 level

If someone is how are you scheduling the NTBACKUP ?

DSMSCHED.LOG

Incremental backup of volume 'SYSTEMSTATE'
11/23/2008 09:02:11 ANS1948E The Microsoft volume shadow copy system
components could not be queried.

11/23/2008 09:02:11 ANS1948E The Microsoft volume shadow copy system
components could not be queried.

DSMERROR.LOG

11/24/2008 13:47:07 ANS5250E An unexpected error was encountered.
   TSM function name : VssRequestor::queryWriters
   TSM function      : GetComponentInfo() returned E_OUTOFMEMORY
   TSM return code   : 4344
   TSM file          : vssreq.cpp (5791)
11/24/2008 13:47:08 ANS5250E An unexpected error was encountered.
   TSM function name : vssQueryComponents
   TSM function      : queryWriters() returned '4344'
   TSM return code   : 4344
   TSM file          : vssback.cpp (797)
11/24/2008 13:47:09 ANS1948E The Microsoft volume shadow copy system
components could not be queried.

11/24/2008 13:47:09 ANS1948E The Microsoft volume shadow copy system
components could not be queried.

Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbrown AT cenhud DOT com <mailto:tbrown AT cenhud DOT com>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255


This message contains confidential information and is only for the
intended recipient.  If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message
to the intended recipient, please notify the sender immediately by
replying to this note and deleting all copies and attachments.  Thank you.

This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.