[ADSM-L] SYSTEMSTATE is much bigger in TSM Client 6.1.0 for Windows 2003

Hello TSMAdmins,
I have reported problem to IBM.
This is a result of partial investigation:
...

------------------------------------------

Env.: Windows 2003 servers -> upgrade from 5.5.1 to 6.1.0

----------------------

Prb.:

After upgrade from 5.5.1 to 6.1.0 systemstate backup is significantly

larger.

----------------------

Done:

1.)

Tested it but could not reproduce the problem (Windows 2003 EE)

2.)

Requested (for comparable systems):

(a) dsmadmc outputs (occupancy)

(b) dsmc q systemstate

    dsmc q systemstate -inact

    dsmc q backup systemstate

    dsmc q backup systemstate -inact

3.)

Findings -> other components are comparable excepth for Bootable which

has almost twice the size:



   158,663,440  B  10/04/2009 02:00:17    BRANCHES    A  FULL MALL360BR\

                SystemState\NULL\System State\SystemState\TSM\FULL\

                20091004020017\Top\SystemState\Event Logs\Event Logs\1\

                Event Log Writer

*  720,807,905  B  10/04/2009 02:00:17    BRANCHES    A  FULL MALL360BR\

                SystemState\NULL\System State\SystemState\TSM\FULL\

                00000000000000\Top\SystemState\Bootable\      <---- (!)

                Bootable System State\0\Bootable

   234,905,600  B  10/04/2009 02:00:17    BRANCHES    A  FULL MALL360BR\

                SystemState\NULL\System State\SystemState\TSM\FULL\

                20091004020017\Top\SystemState\Bootable\ntds\null\1\NTDS



   141,979,920  B  10/04/2009 05:05:32    BRANCHES    A  FULL RIGGABR\

                SystemState\NULL\System State\SystemState\TSM\FULL\

                20091004050532\Top\SystemState\Event Logs\Event Logs\1\

                Event Log Writer

*1,263,987,365  B  10/04/2009 05:05:32    BRANCHES    A  FULL RIGGABR\

                SystemState\NULL\System State\SystemState\TSM\FULL\

                00000000000000\Top\SystemState\Bootable\     <---- (!)

                Bootable System State\0\Bootable

   232,808,448  B  10/04/2009 05:05:32    BRANCHES    A  FULL RIGGABR\

                SystemState\NULL\System State\SystemState\TSM\FULL\

                20091004050532\Top\SystemState\Bootable\ntds\null\1\NTDS

4.)

Also compared number of files and sizes with active versions only

(q backup systemstate) and could not find substantial differences.

Counter error only perhaps?
------------
I am waiting now for L2 support.
Maybe somebody has an any information or suggestions for me?
Regards,


Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme 
DOT com<mailto:G.Solonovitch AT bkme DOT com>

Please consider the environment before printing this Email


Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."
[ADSM-L] SYSTEMSTATE is much bigger in TSM Client 6.1.0 for Windows 2003 SE
