Data storage allocation considerations

Last Updated : Oct 22, 2024 |

Consider the following before working with data storage allocation:

  • A full maintenance backup should be performed before changing the data storage allocation configuration.

  • Before changing data storage allocation values, you must disable data collection and set the CMS state to single-user mode.

  • You can make ACD system changes by running the cmssvc command and selecting the swsetup option. If you do this, you must check the data storage allocation settings to ensure that storage is set for any new or modified entities. For example, when activated, the Call Vectoring feature requires data storage space for VDNs and vectors. Changing the release number for the ACD system might change the number of measured entities and affect the storage allocation for each entity.

  • When determining the amount of storage space needed, remember that future growth of items, such as trunk groups or splits/skills, need to be taken into account.

  • If a Data Storage Allocation window is modifying data in the PC Client, do not open a second Data Storage Allocation window. Wait for the first window to finish the modifications as performing simultaneous modifications through two Data Storage Allocation windows can result in damage to data tables.

  • Use the Free Space Allocation page to view the utilization of disk space before making changes to data storage allocation settings. If changes are made to the data storage allocation settings, free space is automatically adjusted.

  • The length of the intrahour interval affects the amount of disk space required to store intrahour data. For example, an intrahour interval of 30 minutes requires twice the amount of disk space than an intrahour interval of 60 minutes.

  • If the Call Vectoring feature is not enabled, the fields corresponding to call work codes, vectors, and VDNs are not displayed.

  • The data storage values determine how much data is available for running historical reports. For example, if weekly and monthly data is not saved, weekly or monthly reports display no data.

  • Disk space affects the amount of historical data that can be stored. The following list provides the maximum durations possible when storing historical data:

    • Intrahour - 370 days

    • Daily - 1825 days (5 years)

    • Weekly - 520 weeks (10 years)

    • Monthly - 120 months (10 years)