VictorSTS's latest activity
-
VictorSTS replied to the thread CEPH client only node.With just 3 nodes, if one fails no rebalancing will happen. There will be some rebalancing if one OSD fails, though. Check this thread with some detailed expanations about this [1]. Add it to the cluster then with OSD's and let Ceph deal with... -
VictorSTS replied to the thread Needed: best practices when updating server that has shared storage in cluster.Hehe, no problemo. We all sometimes need a hand to find out that from time to time we all become John Snow for a while and "know nothing".
-
VictorSTS replied to the thread Needed: best practices when updating server that has shared storage in cluster.Sorry, still don't get the full picture... ;) Ok, there's an external storage that you connect via iSCSI to... one PVE of the 22 in your cluster? another PVE that does not belong to the cluster? You mention it is "shared to the rest of the...
-
VictorSTS replied to the thread Needed: best practices when updating server that has shared storage in cluster.Sorry, I don't fully understand how is your cluster configured, which storage(s) are you using and what are your trying to accomplish. I would need details to give you accurate recomendations.
-
VictorSTS replied to the thread Needed: best practices when updating server that has shared storage in cluster.If all your storage is in a single iSCSI box, you have a single point of failure, which kinda defeats the whole purpose of a cluster. You will need to plan for downtime, stop everything on PVE, log out iSCSI from each PVE (not sure if needed...
-
VictorSTS replied to the thread Understanding CEPH in a 3 Node Cluster with 12 OSDs.3 node Ceph works beautifully, but has very limited recovery options and requires a lot of spare space in the OSD if you want it to self-heal. I will try to explain myself to complement @alexskysilk replies: It can't: the default CRUSH rule...
-
VictorSTS replied to the thread Understanding CEPH in a 3 Node Cluster with 12 OSDs.If you mean about the total Ceph usage, then yes, 10.5TiB * 3 = ~31.5TiB. The usable capacity is for the whole cluster: you store 3 copies of every bit, one copy in each of your 3 servers. Thats why I divided by 3 the whole gross capacity of all...
-
VictorSTS replied to the thread Understanding CEPH in a 3 Node Cluster with 12 OSDs.How many OSD do you have in each host? If you are only using size=3 replicated pools, your net space would be ~41.92TiB/3 = 13.97TiB. Keeping in mind that in general Ceph will start complaning when an OSD is at 85% full, the net usable capacity...
-
VictorSTS reacted to Chris's post in the thread How to backup Linux clients without Proxmox Backup client? with
Like.
Ah, I see... There were already some users in the forum which did perform backups using the PBS client inside the WSL, but this comes with its own set of issues [0, 1]. Please note: neither do we test such approaches, nor is this expected to... -
VictorSTS replied to the thread How to backup Linux clients without Proxmox Backup client?.I know it won't run natively, but I'm in the hopes that the all-in-one versión of proxmox-backup-client can run without much trouble inside Windows' WSL enviroment, which essentially is an Ubuntu. That probably won't allow backups of Windows...
-
VictorSTS replied to the thread Ceph spams console during network issue..I know your pain... Try with dmesg -n 1. From man dmesg: -n, --console-level level Set the level at which printing of messages is done to the console. The level is a level number or abbreviation of the level name. For all...
-
VictorSTS replied to the thread How to backup Linux clients without Proxmox Backup client?.Meanwhile the statically linked client is ready, take a look at this third party implementation in Go [1]. Haven't used it, so no idea how/if it works. [1] https://forum.proxmox.com/threads/proxmox-backup-client-for-windows-alpha.137547/
-
VictorSTS replied to the thread Slow backup with PBS.So this backup was done without dirty-bitmap because the VM is off before the backup. QEMU had to read the whole disk, compress it and get the checksum of each block. If you check the log, your PVE took ~32 minutes to read just ~58 GiB, which is...
-
VictorSTS replied to the thread create storage failed: mypbs: error fetching datastores - 500 Can't connect to mypbs:8007 (Connection timed out) (500).Double check that your PVE hosts can reach your PBS server at 10.178.53.135 port 8007/tcp. That error simply means that your PVE can't reach that PBS IP : port. Check routes, firewall, etc.
-
VictorSTS replied to the thread reboot whole cluster because of CPU throttling, after new update.I've had similar behavior when using NFS storage, either for VMs/CTs or for backups and NFS didn't work properly on some node(s): pvestatd had to wait a lot for the storage to reply or timeout, making the webui to show question marks. I would...
-
VictorSTS replied to the thread [TUTORIAL] what is the best way to encrypt the disks.So obvious that my brain completely forgot that's the way o_O