Article ID: 119442, created on Jan 1, 2014, last review on May 4, 2014

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

We are trying to migrate PBA-S 4.5 to a new container based on CentOS6 64-bit:

~# hspc-mn-backup -m –d root@[TMP_IP]

However we are running out of space because when running the hspc-mn-backup the database dump file is extremely large.

Cause

Migration utility "hspc-mn-backup" with option "-d" uses mysqldump for dumping the database. The database dump is big because one of the following reasons:

  1. A lot of old unused data.
  2. Mysql corruption that causes database dump increase. Try dumping the database with mysqldump to get its real size. Try the following command to dump the database:

    ~# mysqldump aspc --extended-insert=false > aspc.dump.date +%F.%s.sql

Resolution

  1. Remove old unused data with "Data Retention":

    PCC > Top > Configuration Director > Miscellaneous Settings > Data Retention

  2. If there is not much data in PBA-S but the database dump is extremely big, then you should verify mysql server and fix the corruption. Restore a database from a backup, if exists.

Search Words

db_dump.sql

mysqldump

cannot migrate to CentOS 6

huge mysql dump

hspc-mn-backup

big mysql dump

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF