borg key import. can it work with something else than ssh?

Exploring Borg Backup Key Import: Alternatives to SSH

Borg Backup, a powerful deduplicating backup program, predominantly utilizes SSH (Secure Shell) as its primary transport method for connecting to backup locations. However, many users inquire whether it's possible to use alternatives to SSH for key imports and data transfers. In this article, we will delve into the options available for Borg Backup regarding key imports and transport methods beyond SSH.

Understanding Borg Backup Key Import

What is Borg Backup?

Borg Backup is designed for efficient and secure backup creation, which is especially useful in scenarios where data deduplication can save storage space. The typical workflow involves the Borg client making a connection to a backup server to execute operations such as backups or restores.

Key Import Mechanism

Borg utilizes keys (either SSH keys or repokey) to configure secure access to repositories. The repokey system allows you to manage access without relying solely on SSH. However, if you want to connect to remote repositories, SSH remains a common choice, mainly because it provides encryption and secure access.

Alternatives to SSH for Borg Backup

While SSH is commonly used, Borg does support some alternatives for connecting to remote storage. Here are a few options:

1. SFTP (Secure File Transfer Protocol)

For users who need an alternative to SSH, SFTP can effectively be employed. SFTP operates over SSH but can handle scenarios where SSH might not be directly available. Users can configure Borg to connect through SFTP as an alternative transport method, utilizing password authentication in lieu of SSH key-based authentication.

2. Local Filesystem

For local backups, Borg can simply use the local filesystem. In this scenario, no SSH keys are required since the data is backed up directly on the same machine or a physically accessible server.

3. Cloud Storage Solutions

Recent developments have introduced support for using cloud storage services as the backup target. Borg works with Rclone, which enables connections to over 70 cloud providers without requiring SSH. This inclusion allows users to back up their data to various cloud platforms like Google Drive or Dropbox efficiently.

4. Other Protocols

Beyond SFTP, users can explore various other protocols depending on their server configurations. Should the Borg repository be accessible through different means, such as WebDAV, users might be able to configure their environment accordingly—though with limitations compared to the native SSH connections that Borg was originally designed for.

Limitations of Non-SSH Methods

While alternatives to SSH exist, they may not always offer the same level of efficiency, security, or compatibility. For instance, using local filesystem backups does not allow remote access, whereas cloud services may incur extra complexity during setup. Furthermore, certain features available in Borg’s SSH implementation may not translate seamlessly to other protocols.

Conclusion

In summary, while SSH is the traditional transport method for Borg, users have viable alternatives such as SFTP, local storage, and cloud backups using Rclone. Each method comes with its unique set of advantages and limitations, and the choice largely depends on user requirements and the environment in which Borg is deployed. Ultimately, as backup needs evolve, exploring these alternatives can provide enhanced flexibility and security in managing data.

For further details, you can refer to the official Borg Documentation and community discussions on platforms like GitHub and support forums.