BACKUP-MANAGER-UPLOAD(8)

πŸ“¦
version 0.7.14 Β· 3 versions
, in debian trixie, ubuntu resolute, ubuntu stonking

πŸ’– BACKUP-MANAGER-UPLOAD πŸ’–

okay bestie, welcome to backup-manager-upload β€” this is the backup-manager-upload manual page from section 8, and she's here to scoot your backup archives up to a remote host. multiprotocol, multi-vibe, no cap. πŸ¦‹


✨ NAME ✨

backup-manager-upload β€” Multiprotocol uploader for backup-manager. πŸ‘‘


🌸 SYNOPSIS 🌸

backup-manager-upload [options] date

πŸŽ€ DESCRIPTION πŸŽ€

So here's the tea: backup-manager-upload will upload all the archives generated on the given date to the specified host, using either ftp or scp. πŸ’…

And it's not just those two, bestie β€” you can also use this program for uploading data to an Amazon S3 account. main character energy fr fr.

Some metadates are available too, like "today" or "yesterday", because remembering actual dates is lowkey a lot. 😭


πŸ‘‘ REQUIRED ARGS πŸ‘‘

These ones are not optional, queen. you will be providing them.

  • --mode=transfer-mode β€” Pick the transfer mode you wanna use: ftp, scp, or s3.
  • --host=hostname1,hostname2,...,hostnameN β€” Give a whole list of remote hosts to connect to. the more the merrier ✨
  • --user=username β€” The user to use for the connection.

πŸŽ€ OPTIONAL ARGS πŸŽ€

the little extras. the garnish. the accessories. 🫢

  • --password=password β€” The ftp user's password. only needed for ftp transfers, so if you're not doing ftp you can literally just not.
  • --key=path_to_private_key β€” The ssh private key file to use when opening the ssh session for scp transfer. obviously only needed for scp transfer mode. if you don't specify a key file, the user's default private key will be used. πŸ—οΈ
  • --directory=directory β€” Where on the remote host the files get uploaded. Default is /backup/uploads.
  • --bucket=bucket β€” Sets the bucket name for the Amazon S3 service backup into. πŸͺ£
  • --root=directory β€” The local directory where files are. Default is /var/archives.
  • --gpg-recipient=gpg-recipient β€” Select the gpg public key for encryptiong the archives when uploading with the method ssh-gpg. This can be a short or long key id or a descriptive name. The precise syntax is described in the gpg man page. πŸ”
  • --list β€” Just list the files to upload. no uploading, just looking. window shopping, if you will. πŸ™ˆ
  • --ftp-purge β€” Purge the remote directory before uploading files in FTP mode. bye bye old files ✨
  • --s3-purge β€” Purge the remote directory before uploading files in FTP mode.
  • --ssh-purge β€” Purge the remote directory before uploading files in SSH mode.
  • --verbose β€” Flag to enable verbose mode. she will talk. a lot. πŸ—£οΈ
  • date β€” Date pattern to select some files to upload. can be a valid date (YYYYMMDD) or 'today' or 'yesterday'.
ngl bestie, --s3-purge says "in FTP mode" in the original page and I am simply reporting the lore as written. don't come for me πŸ’€

πŸ’€ ERROR CODES πŸ’€

If something goes wrong during an upload, backup-manager-upload will exit with a non null value. In such a case every error messages are sent to STDERR. not the vibe, but at least you'll know. 😭

Here are the possible error codes:

  • bad command line (wrong arguments) : 10
  • FTP transfer failure : 20
  • SCP transfer failure : 21
  • S3 transfer failure : 22
  • Unknown upload method: 23

🌈 SEE ALSO 🌈

  • backup-manager(3)

πŸ’œ AUTHORS πŸ’œ

  • Alexis Sukrieh β€” main code and design
  • Brad Dixon β€” Amazon S3 upload method
  • Jan Metzger β€” ssh-gpg upload method

and that's the whole page, bestie!! this one lives in the backup-manager-upload source, perl v5.40.1, dated 2025-04-11. go forth and upload responsibly πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά

πŸ“¦ where this page comes from