Cisco Cisco Unified Contact Center Enterprise 9.0(1) Guia Da Instalação

Página de 153
Backup, network copy, and restore – Technology Refresh only
Network copy speed is dependent upon the speed of the network and the speed of the disk
sub-system. The faster the network the faster the network copy.
Backup/Copy/Restore Time (Hours)
Database Used Size (GB)
.5 – 1
10
1.5 – 2.5
20
2 - 4
40
3.5 – 5
70
Note:
• The values in the Database Used Size in the table above are based on the amount of disk
space used by the Source database, not the size of the disk it resides on.
• The Backup/Copy/Restore Times in the table above assumes the network meets the minimum
requirements of the 
 (http://www.cisco.com/en/US/
products/sw/custcosw/ps1844/products_implementation_design_guides_list.html).
• For Technology Refresh upgrades, have the fastest network possible (gigabit through one
network switch) between the source and the destination machines. Use of a crossover cable
is not supported because it lacks buffer memory and can cause data loss.
Run timings, Technology Refresh and Common Ground
The conversion should take place in less than a half hour—in most cases, much less. The actual
time can vary based on the parameters discussed in the 
.
Performance considerations
During internal testing, hyper-threading has consistently doubled the time it took the database
migration to complete; therefore, to minimize migration time you should disable hyper-threading.
Ways to reduce data migration time
You can reduce data migration time with the following methods.
Reduce database size:
Purge the Logger DB of all data already replicated to the HDS (25 GB or less)
Remove redundant records, especially RCD, RCV, TCD, and TCV tables via ICM Purge
Utility and/or SQL Query Analyzer
Upgrade Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 9.0(1)
36
Chapter 5: Unified ICM/Contact Center 9.0(1) upgrade time and space requirements
Time guidelines and migration performance values