Hi Win200x Server Backup Techs, I'd be interested in info on this too. I just went through this, forced to move NT disks around. Our one big shared network disk on Win2003 Server filled up and first we split off to a 2nd disk, then moved to a much larger single disk chunk again, all on an IBM SAN. I kept the disk id E: the same on the same server name etc, but just couldn't stop Tivoli from backing up the whole thing again and again. After doing our normal 6 week incremental and an image backup in case etc, I created a FLUSH domain with 2 day retention and smaller version settings etc, moved the Win2003 server to that domain, and flushed out the older FULL backups. I then moved it back to the domain it was in.
So what "flag" does the Win200n Tivoli client use to backup a file again, besides update date or archive flag? Thanks.. Charlie Hurtubise Tecsys Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David McClelland Sent: Thursday, May 12, 2005 6:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Re Windows 2000 client reconfiguration Hi Farren, Been here before ourselves... might be interesting/useful to work out why the TSM client believes the file has changed. Run a backup of the files that you believe it should *not* be backing up but is, but with a trace enabled (hmn, I forget the exact traceflag we used now - might be worth you taking a look at Richard Sims' (not-so!)Quick Facts for the correct one) and this will tell you which attribute it is that it thinks has changed, be it NT permissions, modified date etc... I remember uncovering a somewhat undocumented '-testflag SKIPNTSECURITYCHANGES' during this saga last year which did exactly what the name suggests... Hope that helps point you in the right direction... Rgds, David McClelland Shared Infrastructure Development Reuters 85 Fleet Street London EC4P 4AJ -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: 12 May 2005 09:08 To: ADSM-L@VM.MARIST.EDU Subject: Re Windows 2000 client reconfiguration Morning all TSMers Running TSM 5.1.6.2 on a Solaris server. Attached to 1*3494 library with two*3590H1A drives. I have a possible problem here. One of the sys admins for the Windows 2000 servers has informed me that they are going to need to replace an entire Windows 2000 server due to severe hardware issues that they have been experiencing. No amount of support has fixed the problem and hence the drastic move. The server has got some 820,000 files on it amounting to approximately 450GB. Here is what we want to do. Configure a new server and copy the data across in such a way that it doesn't look like it's changed. The new server will have the exact same Node name, file system layout etc. I don't really want to be faced with backing up the entire server all over again as we are getting low on both tape space in the library and database space. This was not something I had foreseen. >From what I have been told, early tests have not been promising and TSM still thinks files have changed even if the last change date/time etc has not altered. Does anyone have any experience with this or any advice they can give that may help us avoid a long backup that will hog system resources? Many thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley & Sons, Ltd ###################################################################### The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ###################################################################### ----------------------------------------------------------------- Visit our Internet site at http://www.reuters.com To find out more about Reuters Products and Services visit http://www.reuters.com/productinfo Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
