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 <[EMAIL PROTECTED] OM> To Sent by: "ADSM: [EMAIL PROTECTED] 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/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] (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 <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/02/2003 06:03 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] 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