Migration speed will greatly depends on the speed of the source and target systems. Quest can not provide any baseline recommendations regarding this. Ensure that migration proof of concept (POC) testing has been performed and documented to determine any speed throughput benchmarks prior to reaching out to support.
Quest would suggest reaching out to Microsoft and HCL/Lotus for any assistance with the performance of your environment.
MNSP speed depends on many factors that are outside of support for the product:
Note: Phone/email/chat support is not specifically trained in advising upon deployment, configuration or optimization of a migration. If you do not find assistance within the videos, user guides or online resources. Then reach out to your Quest account manager or a sales representative and request assistance from the Professional Sales Organization (PSO) within Quest Support that are specifically trained and experienced in performing these requests.
When discussing performance, migration speeds are generally measured in GB/hr, but that value has limited meaning unless we understand the composition of the content. It is important that the migration job is planned specifically for the type of data that is being migrated. The best advice is “test early and test often” to find out as soon as possible what sort of datasets are to be migrated. By running multiple tests early, results then can be compared which will help influence migration performance strategies.
By having baseline migration benchmarking performed, it will provide the data on what is expected versus achieved for a database migration.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center