Manager [mailto:[EMAIL PROTECTED] Behalf Of
Steve Schaub
Sent: Thursday, February 03, 2005 12:46 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migrating Windows File Data Question
Charles,
I have run into it - be prepared for a huge expiration run in the near
future.
Also, if you use client journaling
]
Sent: Wednesday, February 02, 2005 5:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migrating Windows File Data Question
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
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
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 Co
