-
Notifications
You must be signed in to change notification settings - Fork 217
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
Backup fails to upload through FTP protocol #283
Comments
Thanks a lot for reporting, look like we should add FTP testing on our github actions |
I faced the same problem with backup via FTP: OS: ALT Server 10.0
|
found the root reason, look like |
Merged
Slach
added a commit
that referenced
this issue
Oct 24, 2021
# v1.2.0 INCOMPATIBLE CHANGES - REST API `/backup/status` now return only latest executed command with status and error message IMPROVEMENTS - Added REST API `/backup/list/local` and `/backup/list/remote` to allow list backup types separately - Decreased background backup creation time via REST API `/backup/create`, during avoid list remote backups for update metrics value - Decreased backup creation time, during avoid scan whole `system.tables` when set `table` query string parameter or `--tables` cli parameter - Added `last` and `filter` query string parameters to REST API `/backup/actions`, to avoid pass to client long JSON documents - Improved `FTP` remote storage parallel upload / download - Added `FTP_CONCURRENCY` to allow, by default MAX_CPU / 2 - Added `FTP_DEBUG` setting, to allow debug FTP commands - Added `FTP` to CI/CD on any commit - Added race condition check to CI/CD BUG FIXES - environment variable `LOG_LEVEL` now apply to `clickhouse-backup server` properly - fix #280, incorrect prometheus metrics measurement for `/backup/create`, `/backup/upload`, `/backup/download` - fix #273, return `S3_PART_SIZE` back, but calculates it smartly - fix #252, now you can pass `last` and `filter` query string parameters - fix #246, incorrect error messages when use `REMOTE_STORAGE=none` - fix #283, properly handle error message from `FTP` server - fix #268, properly restore legacy backup for schema without database name - fix #287
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
We're trying to upload backups created with
clickhouse-backup
to our remote location, with a similar configuration for both SFTP and FTP.Whilst the first one works like a charm, we want to use FTP as it's faster.
However, we get an error doing it with FTP:
Our
config.ftp.yml
config file below (sensitive information redacted for security reasons):Now follows the trace of the command, with additional debug information:
Looks like the folder is not being created before trying to be accessed.
As I said, with our SFTP configuration, the backups are correctly updated.
For the sake of completion, I'll attach below the SFTP configuration file:
The text was updated successfully, but these errors were encountered: