AW: Preventing re-backup of NT drive copied with scopy
2003-12-10 10:41:28
I guess:
have a look at TSM - assigned Filespacename:
Query Filespace your_nodename
This gives you a view what TSM found to be different
and maybe an opportunity to change it.
I recall that with NT4 and an older version of TSM
the LABEL of the disk/FileSystem made the difference as well.
regards
Juraj
-----Ursprüngliche Nachricht-----
Von: Steven Bridge [mailto:ccaasub AT UCL.AC DOT UK]
Gesendet: Mittwoch, 10. Dezember 2003 15:29
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Preventing re-backup of NT drive copied with scopy
A drive on an NT 4 fileserver which was mapped to a RAID unit containing
about 120 GB of data has been copied to a new RAID unit with greater
capacity. The data was copied using scopy using appropriate flags to
preserve permissions and modification dates. The original drive letter
was then re-assigned to the copy of the data.
Unfortunately, it now looks like TSM ( client 5.1.0.1 , server 5.1.6.3 )
is backing up everything in the drive again. With a throughput of
only about 1 GB an hour, it looks like it is going to take several days
to complete.
Is there anyway to persuade TSM that that it already has the data ?
Is it because the drive itself has a new modification date that
everything else underneath is seen as new ?
+----------------------------------------------------------------------+
Steven Bridge Systems Group, Information Systems, EISD
University College London
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- AW: Preventing re-backup of NT drive copied with scopy,
Salak Juraj <=
|
|
|