Bill, your read of the client manual is correct. For Windows 2003, TSM 5.2
uses the Microsoft VSS (Volume Shadowcopy Service) to back up system state
and system services, versus the "legacy" methods used in TSM 5.1 and
earlier to back up what we called the "system object".

In addition, the Windows 2003 system state/service backups use a different
transaction protocol that doesn't pin the server recovery log for
extensive periods of time, as might the "system object" backup method.
This support required changes on the server side as well, and thus the
requirement for a 5.2 server.

You can use the 5.1.6.x client and system object backup method for backing
up the Windows 2003 to a TSM 5.1 server.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Bill Boyer <bill.boyer AT VERIZON DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/11/2003 12:00
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Backing up Windows2003 Server with Client 5.2


I ran a full backup of a Win2003 server last night with the 5.2.0.2
client.
The event shows as failed, but the backup actually backed up nothing.
Here's
the stats:

09/10/2003 22:11:48 --- SCHEDULEREC STATUS BEGIN
09/10/2003 22:11:48 Total number of objects inspected:   44,113
09/10/2003 22:11:48 Total number of objects backed up:        0
09/10/2003 22:11:48 Total number of objects updated:          0
09/10/2003 22:11:48 Total number of objects rebound:          0
09/10/2003 22:11:48 Total number of objects deleted:          0
09/10/2003 22:11:48 Total number of objects expired:          0
09/10/2003 22:11:48 Total number of objects failed:      44,113
09/10/2003 22:11:48 Total number of bytes transferred:     2.44 GB
09/10/2003 22:11:48 Data transfer time:                  139.91 sec
09/10/2003 22:11:48 Network data transfer rate:        18,331.90 KB/sec
09/10/2003 22:11:48 Aggregate data transfer rate:      4,511.33 KB/sec
09/10/2003 22:11:48 Objects compressed by:                    0%
09/10/2003 22:11:48 Elapsed processing time:           00:09:28
09/10/2003 22:11:48 --- SCHEDULEREC STATUS END
09/10/2003 22:11:48 --- SCHEDULEREC OBJECT END BD72200 09/10/2003 22:00:00
09/10/2003 22:11:48 Scheduled event 'BD72200' completed successfully.

In the server log (this is a TSM 5.1.7.1 server on AIX 4.3.3) I see
numerous:

09/10/2003 22:06:49      ANR9999D smnode.c(19134): ThreadId<20> Session
38868 for
                          node NWTRACKIT : Invalid filespace for backup
group
                          member: 3.
09/10/2003 22:06:49      ANR0444W Protocol error on session 38868 for node
                          NWTRACKIT (WinNT) - out-of-sequence verb (type
Data)
                          received.
09/10/2003 22:06:50      ANR9999D smnode.c(19134): ThreadId<31> Session
38883 for
                          node NWTRACKIT : Invalid filespace for backup
group
                          member: 3.
09/10/2003 22:06:50      ANR0444W Protocol error on session 38883 for node
                          NWTRACKIT (WinNT) - out-of-sequence verb (type
Data)
                          received.
09/10/2003 22:06:50      ANR0484W Session 38868 for node NWTRACKIT (WinNT)
                          terminated - protocol violation detected.
09/10/2003 22:06:50      ANR0484W Session 38883 for node NWTRACKIT (WinNT)
                          terminated - protocol violation detected.


Looking at the 5.2 client manual, it says that to backup the "system
Services" I need a TSM 5.2 server?!??!!? Does that mean I can't back up a
Win2003 server unless I'm at 5.2 all the way around? This is an AIX4.3
server so I can't upgrade it to TSM 5.2.

Bill Boyer
"Some days you are the bug, some days you are the windshield." - ??