The PCT real time migration process is running extremely slow. One example of a migration showed a profile with an approximate size of 20GB taking 8 hours.
Although the root cause is not known it was found that the destination machines that were being migrated to had corruption in the window security database. It would appear that in part this created a performance hit on the real time migration leading to approximately only 600k of data being transferred a second. For a larger sized personality this would push out the duration time for the migration to unacceptable levels.
c. Click OK when you receive the following message:
You should only run Repair on damaged or corrupted databases. Repair will not apply information in the transaction log files on the database, and may cause information to be lost. Do you wish to proceed?
Further to this the following actions were performed in order to optimise performance of the migration:
(1) The DS was configured to perform the real time migration as per the below Altiris kb:
(3) PCT was utilised purely for the settings/printers portion of the profile migration and via the DS run script task and custom data source as configured in (1), MS Robocopy was used to migrate the majority of data as this did not appear to have a performance hit.
All versions of PCT
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.