Steven,
Make sure that SCopy preserved the *inheritance* security properties.
We've migrated Windows servers in the past using either SCopy or XCopy /O.
On the target server, the files and folders had the correct permissions,
but they were "applied" rather than "inherited". I'm not sure which tool
caused that because we didn't discover it until much later. But that
could be enough to provoke a full backup.
Tab Trepagnier
TSM Administrator
Laitram LLC
Steven Bridge <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/10/2003 08:29 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: 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
