-
Notifications
You must be signed in to change notification settings - Fork 291
CA-409710: Modify the default backup parameters #6440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
9c41a7e
to
97f1b79
Compare
97f1b79
to
1b24182
Compare
The backup VDI is created by this script. So another solution is to create a larger VDI or to decide dynamically how many generations to keep. |
Is it possible to make the backup disk larger? 500 MB seems to be quite small. Perhaps double the disk instead of half the back up file limit? |
The number of generations kept is only the default and there is an option to override this. So what this change does is changing the default. But like I said above, we could also change the size of the VDI. The script already emits an alert when it is running low on space.
A change here obviously would only take effect when no VDI already exists.
|
The current default count of metadata backup files is 25. This number is too many. For the customer in XSI-1873, the backup disk is 500 MB, and each backup file is about 35 MB. So it can't keep 25 backup files. A quick solution is to modify the backup parameters, including: 1. Reduce the default count of metadata backup files to 12. 2. Increase the backup VDI size to 1024 MB so it can keep more backup files. Signed-off-by: Bengang Yuan <[email protected]>
1b24182
to
d50d5ac
Compare
The current default count of metadata backup files is 25. This number is too
many. For the customer in XSI-1873, the backup disk is 500 MB, and each backup
file is about 35 MB. So it can't keep 25 backup files.
A quick solution is to modify the backup parameters, including: