When you say, "I had already changed the filespace to unicode ...", what
exactly do you mean? If you mean that you set autofsrename to yes, then
yes, this cause the old file spaces to be renamed and new unicode file
spaces to be created, which results in a full backup.

>From an Admin client, do a QUERY FILESPACE for the node. Do you see both
unicode and non-unicode file spaces for this node?

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.eyebm DOT com (change eye to i to reply)

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




Lisa Cabanas <cabanl AT MODOT DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/02/2003 06:03
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        after updating client code 4.2.1.9 --> 5.1.5.9 on NT4,  
       get new
full b/u on client?



I guess I was sleeping when I updated the previous 25 clients and didn't
notice, but I noticed this morning that all of the clients I updated the
code on yesterday were doing a full backup last night.  I had already
changed the filespace to unicode, which would be the only thing of note
that was different in the option file, so I don't understand why TSM
thought that all of the files were different.

Has anyone else experienced this & is this behaving as expected, or do I
need to look more deeply into this?

TIA

-lisa