Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


How to use and make Block Storage accessible remotely
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

How to use and make Block Storage accessible remotely

scookescooke Member
edited November 7 in Help

Hi. I'm stumped. If someone more experienced could share a few bits of advice, I'd appreciate it. I signed up with Smarthost for a 2TB block storage service. I followed their tutorials to make the 2TB parition for the block storage. My question is - now what? I tried installing some docker apps on the main partition to use the block storage, but the partition for that is only 20GB, and it quickly crashes when trying to update anything due to running out of space. I just can't get my head around how to make that block storage accessible to other servers or apps, for storage; it shouldn't even need anything from the main partition, right? I'm used to just using an IP4 address and local destination, but for some reason it isn't working for the block storage partition. It's about the syntax I suspect - I don't know how to write out the syntax to let VPS1 use the block storage for remote backup. Tips, or tut suggestions are welcome! Thank you!

EDIT: It is block storage, not object storage. Sorry for that. I'm posting below the pertintent order specs:
VPS - KVM - Linux - NVME SSD - Block Storage
Memory: 6GB - 6144MB
Disk Space: 20 GB
Block Storage: 2048GB - 2TB
Bandwidth: 2000GB/Month
CPU: Medium - 2 Theads
Extra IPv4 Address: No Extra IPs

Comments

  • Do you even know what you bought?

    Because putting "Smarthost" and "Object Storage" into Google returns... this topic.

    Object Storage is generic name, for many different services/protocols/types.

  • "Object Storage" itself can be means any, Do you mean S3 Compatible Storage or ?

  • Sorry @JabJab and @reikuzan, I meant block storage. Do I know what I bought... apparently not! But it IS 2TB of block storage that I wanted.

  • JabJabJabJab Member
    edited November 7

    So you bought a 2TB of "hard disk space" and it's up to you how to "share" it - this is why it comes with whole VPS and not only "URL" to access.

    S3 and (f.e.) MinIO?
    Straight up FTP server for backups?
    Export as NFS and mount it on server you plan to backup?

    You need to read and decide, everything has pros and cons.

    Thanked by 1scooke
  • You know what. I'm gonna take another stab at this. IGNORE This Post!!!

  • @scooke said:
    Hi. I'm stumped. If someone more experienced could share a few bits of advice, I'd appreciate it. I signed up with Smarthost for a 2TB block storage service. I followed their tutorials to make the 2TB parition for the block storage. My question is - now what? I tried installing some docker apps on the main partition to use the block storage, but the partition for that is only 20GB, and it quickly crashes when trying to update anything due to running out of space. I just can't get my head around how to make that block storage accessible to other servers or apps, for storage; it shouldn't even need anything from the main partition, right? I'm used to just using an IP4 address and local destination, but for some reason it isn't working for the block storage partition. It's about the syntax I suspect - I don't know how to write out the syntax to let VPS1 use the block storage for remote backup. Tips, or tut suggestions are welcome! Thank you!

    EDIT: It is block storage, not object storage. Sorry for that. I'm posting below the pertintent order specs:
    VPS - KVM - Linux - NVME SSD - Block Storage
    Memory: 6GB - 6144MB
    Disk Space: 20 GB
    Block Storage: 2048GB - 2TB
    Bandwidth: 2000GB/Month
    CPU: Medium - 2 Theads
    Extra IPv4 Address: No Extra IPs

    You need change docker default root folder

    You can change where Docker stores its files including volumes by changing one of its startup parameters called --data-root.

    Thanked by 1scooke
Sign In or Register to comment.