The AUTOFSRENAME option in the client options file is effective only when
the node setting on the server is AUTOFSRENAME=CLIENT. If you set the
nodes to AUTOFSRENAME=YES, then the renames should have occurred
automatically... and yes, it was a "real" option for 4.2 clients.

See the AUTOFSRENAME description in the UPDATE NODE reference for more
info on what this does, and when; and look up the AUTOFSRENAME option in
the client manual for the same kind of info (I won't bother to repeat it
here).

Check the QUERY FILESPACE F=D for one of these nodes. What does it show
for the last backup dates for the file spaces? If the _OLD file spaces
have a recent date, then at least you know why the full backups occurred
last night. But if you set AUTOFSRENAME=YES on the nodes last month, then
off-hand, I do not know why they wouldn't have been renamed at that time
(if indeed that is the case).

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 08:16
Please respond to "ADSM: Dist Stor Manager"


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



I had changed all the clients by a

upd node * autofsrename=yes

and renamed the none-unicode filespaces to _OLD

Node Name       Filespace   FSID Platform Filespace Is Files- Capacity
Pct
                Name                      Type        pace        (MB)
Util
                                                    Unicode?
--------------- ----------- ---- -------- --------- --------- --------
-----
SCDATA13        \\scdata13-    2 WinNT    NTFS         No     104,836.
96.8
                 \d$_OLD                                             7
SCDATA13        \\scdata13-    3 WinNT    NTFS         No     38,145.9
97.6
                 \f$
SCDATA13        \\scdata13-    4 WinNT    FAT          Yes     1,027.8
95.6
                 \c$
SCDATA13        \\scdata13-    5 WinNT    NTFS         Yes    104,836.
97.6
                 \d$                                                 7


I did this at the beginning of March, about a month before I updated the
code and actually put autofsrename=yes into the option files.

Was autofsrename not a "real" option with the 4.2.1.20 client? (I had
typoed before: my server version is 4.2.1.9)

lisa




             Andrew Raibeck
             <storman AT US DOT IBM.C
             OM>                                                        To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     Re: after updating client code
                                       4.2.1.9 --> 5.1.5.9 on NT4,
                                       get new full b/u on client?
             04/02/2003 08:15
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






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