![]() ![]() |
#1
|
|||
|
|||
![]()
We are migrating from SIP AACC 6.4 to 7.03 and found that after the migration our historical database "actual" size (available disk space) has decreased by a factor of 3, even though our hard drives are much larger on the new platform. There's no place to specify the max available disk space, so how do we compensate? Do we artificially inflate our calls-per-hour and re-migrate? Or? Why would an upgrade result in losing 2/3rds of our historical data? Thank you.
|
#2
|
|||
|
|||
![]()
I may have answered my own question. With 6.4 you have a Multimedia and Voice combined database of 600GB (based on sizing parameters); 7.0 breaks out the Multimedia and Voice databases onto two drives. G drive is 600GB (Multimedia) and F drive is now only 200GB (Voice).
|
![]() |
Tags |
aacc, database size, duration, historical storage |
Thread Tools | Search this Thread |
Display Modes | |
|
|