Skip to content
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.

"07/14/2021: mysqldump directory option" #7

Open
ranjeeth12 opened this issue Jul 14, 2021 · 2 comments
Open

"07/14/2021: mysqldump directory option" #7

ranjeeth12 opened this issue Jul 14, 2021 · 2 comments

Comments

@ranjeeth12
Copy link

Is your feature request related to a problem? Please describe.
[Ranjeeth] Yes. When we choose Delphix to take mysqldump from source the dump is by default routed to /tmp folder. Customer installation is such that they have OS level restriction for tmp folder and due to which mysqldump is failing after the limit is reached.

Describe the solution you'd like
[Ranjeeth] Provide an option to customer to chose the dump directory; Otherwise, utilize mount directory for dump and pass on the instructions to increase mount size so that it includes dump size.

Describe alternatives you've considered
[Ranjeeth] Customer added disk space and performed directory level mapping from tmp to another folder. This is a manual workaround and took significant time.

Additional context

@smouhssine
Copy link

A more consistent option would be using a hidden folder (eg: ./tmp) under the staging mount_point to host the backup and remove it once we restore successfully

@arunskurian
Copy link
Collaborator

arunskurian commented Sep 25, 2021

@smouhssine - that's a great idea. I think we can pursue that option.
However, do you think this will slow down the backup process because now the backup file has to be written to Delphix Storage ( NFS + Network delays)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants