Thanks for the confirmation... That's what I thought. Arggg (I understand why) but sure makes Data Moves.
Do other people run into this and what do you do? Thanks again! -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Thorneycroft, Doug Sent: Wednesday, February 02, 2005 3:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Migrating Windows File Data Question Just think of the drive/path as part of the file name. new drive or change in path and tivoli sees it as a new file. If the file no longer exist in the old path, then Tivoli treats it as deleted. Doug Thorneycroft Systems Analyst Computer Technology Section County Sanitation Districts of Los Angeles County (562) 699-7411 Ext. 1058 FAX (562) 699-6756 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Hart, Charles Sent: Wednesday, February 02, 2005 1:36 PM To: ADSM-L@VM.MARIST.EDU Subject: Migrating Windows File Data Question Our Intel team will be using robocopy to move data from one Windows Dick vol to a new one. In the past we have seen TSM Backup the data that was moved, even thought the data has already been backed up before. An example would be... file1.txt has been on the D: Drive and has 10 Active Backup Copies on TSM We move file1.txt to a J: Drive. 1) Does the file1.txt start expiring off because its in a new location and its considered a "new File" to TSM, causing the d:\file1.txt backup history to drop off? 2) Does file one now get associated with its new location on J: Drive and now gets backed up even thought the file has actually not changed? In the past when our Intel group has moved data around and it appears to all gets backed up again due to new location instead the file actually being modified. If anyone could add some insight that would be great.. We don't want to loose our backup history or backup a ton of data that we already have Active / Inactive version of. Appreciate the help!!!! Charles
