Search results

we are looking forward to the same process. additional "problem" is, that we wont migrate all hosts of the existing cluster and retire some of the older hosts. so fo some time, we would have a mixed cluster licensed/unlicensed. still unsure what way to go. hints/tips?

i'd take a look at ansible, puppet, chef etc... we are using ansible for all deployments. as you are speaking of a development environment, maybe there are other deployment mechanisms (github actions and such things) to distribute your certs too. if you use letsencrypt you can automate the...

maybe tailscale (with headscale) and it's namespaces would fit for your needs

^ md1 as I see in the screenshot is root-fs

maybe tune2fs -m0 /dev/md0 frees some bytes for you.... to keep the system working and clean up

I'd try this in first place.

is it stuck or counting? when it's counting just wait till finished. if it's stuck, do a RAM test, maybe the änew RAM has defects.

you dont define the usecase very well but maybe an asynchronous solution would fit. i'd go for nextcloud and tailscale (why expose pve unnecessarily)

you need stackable switches if you want to use active/active and redundancy

what would be the advantage to raid-1?

maybe power consumption is an argument pro ssd. with 2 x ssd you could substitute 5 spinning disks and get more performance.

sorry, Windows habe ich übersehen.... Wenn du NFS als Datastore mit einbindest, ist das im Snapshot mit dabei. Jetzt bin ich bei den Windows-Interna etwas überfragt, wie man Platten ein/aushängt, aber du kannst eine Platte (egal ob "local" oder "datastorage") vor dem Snapshot natürlich...

mountpoint via nfs entweder vom db server oder den nfs auch als extra Maschine

I dont think that you have to zero out the whole disks (taking a long time). I guess your problems are old fs signatures like lvm or zfs. you can wipe those very fast by zeroing the first view bytes on this (please google for details) or probably wipefs the installer formats your partitions...

you can do this. clonezilla is more effective (just copying existing data) and makes misc changes for you. dd can take much longer than clonezilla. rsync method is with least downtime. you can even run several rsyncs in advance with running services. only the last/final rsync must be done with...

principally thats easy, if your linux knowledge is fine. * create new machine in pve * boot this machine into a live system like grml and create and mount the filesystems (lets say to /target) * give the machine a temporary ip, set password for root and start ssh service * on the physical...

install debian and pve on top of it. the debian installer lets you preserve windows. but debian doesnt support zfs root fs

we use evo ssd in large numbers and there is no specific speed problem with it. you just cannot use it in host with high io. I ve seen evos going to 99% wearout within 1 month under certain workloads (dbs mainly). others run for years without problems. and of course there are fast pieces around

one method: boot your host with clonezilla, clone to external drive, restore to new nvme. iirc cloezilla ask if you want to resize partitions to max (if not this can be done later)

even it's true technically speaking, I feel the urge to say that md-raid and ext4/xfs etc served very well and reliable over the last 20 years. the point is, that ceph and ZFS are everything else but slim. so we use depending on the usecase and available power/budget all of these technics. and...