MySQL Instance with a Non-Default tmp Directory

{kb-symptom}
MySQL's {{tmp}} space may be filled up under certain circumstances. The {{tmp}} directory may have limited space if it is put in a non-default location. CDP does not restore all necessary files, and the task fails.

1. Log in to CDP Server.
2. Click "Recovery Points” in the main menu.
3. Select the Agent and the Disk Safe.
4. Select the databases.
5. Click “Restore Selected.”
6. Click “Temporary Instance,” and then select “Specify an Alternate Temp Directory.”
7. Provide a “Temp Directory,” e.g., {{/temporal250mb}}, with no more than 250 MB of free space.
8. Click "Restore."
9. Review the logs during file restoration.
10. CDP does not restore all necessary files, and the task fails.
11. Review Agent logs:
{code}
ERROR],[10.230.106.211:49211],File not restored: '/temporal/r1soft-mysql-restore-tmp-58325331-6c6d-4366-8e8a-505f776b4566/bInnoDB9/table1300.ibd' due to write error: No space left on device
ERROR],[10.230.106.211:49211],file restore error: File System Full ! Restore aborted
12. Review Server Logs
ERROR - TASK(10.230.106.204-Restore Databases)-AGENT: File not restored: '/temporal/r1soft-mysql-restore-tmp-58325331-6c6d-4366-8e8a-505f776b4566/bInnoDB9/table1300.ibd' due to write error: No space left on device
WARN - TASK(Restore Databases): Error restoring file '/var/lib/mysql/bInnoDB9/table1301.frm' Error sending file data
{code}

{kb-resolution}

The issue has been corrected in CDP 4.0.0.

{kb-related-articles}