Interesting 

1)TSM 5.2.2 - No IBM Client support / bug fix - Usually TSM clients do
fine.  We use to run OS/2 Client @ 3.x against a TSM 5 Server.  It's a
support risk . Id ask them what issues were there with more current TSM
clients. 

2) 'Tivoli doe not require a client on the server'. What does GE mean by
this?  The App or backup Server? Ask them to clarify.

3) waveform file will not be updated after it is created, and hence will
only need to be backed up once?
        If using standard TSM Incremental backups then it will only be
backed up once .. 

4) How does the size of a database backup compare to the overall disk
space usage?
         Depend on the flat file backup, not sure if the SQL / NTBackup
removes white space when it backs it up?


5) The instructions for using TSM focus on backing up three folders on
the D drive. Is there any major downside to letting TSM back up the
entire system (as long as we exclude *.ldf and *.mdf files)? 

No - assuming low rate of file change other than the db shouldn't be an
issue.  You'll ensure if new data or naming conv is created you'll get a
copy as opposed to selectively backing files up and missing a change the
app person puts in place. 

Hope this helps 
        
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Thomas Denier
Sent: Wednesday, November 17, 2010 3:00 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] GE Centricity Cardiology INW backups

I have gotten a request to arrange for TSM backup coverage of a GE
Centricity Cardiology INW system. After reading GE's documentation I
have a number of questions for people who are already backing up INW
systems.

Our INW system runs under Windows 2003. We normally use TSM 5.5.1 client
code for this level of Windows, but GE recommends TSM 5.2.2.
What are the pros and cons of accepting GE's recommendation? This
recommendation is accompanied by the puzzling statement that 'Tivoli doe
not require a client on the server'. What does GE mean by this?

The INW system stores report files and waveform files, and has a MS SQL
database containing references to the report and waveform files. Am I
correct in suspecting that a report file or waveform file will not be
updated after it is created, and hence will only need to be backed up
once? The system dumps the MS SQL database contents to flat files and
lets TSM back up the flat files. How does the size of a database backup
compare to the overall disk space usage?

The instructions for using TSM focus on backing up three folders on the
D drive. Is there any major downside to letting TSM back up the entire
system (as long as we exclude *.ldf and *.mdf files)? 

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.