Re: Dangerous installation of bullseye: What shall i do next?
Hey, excellent!
much to my liking, you are coming up with most of the things, i already
do. But never stop improving on them ...
Yes, i use VCS, in my case git. Yes, i use SSD, in my case nvme, yes, i
use SSH (even from a vm to the host), in order to create a simulation of
it for experimentation. (undocumented, but very handy). BTW: That is one
of the reasons to upgrade, bcoz virtualbox is no longer maintained
proper on buster.
Of course, i use snapshots and zfs-auto-snapshot and many services on
top of it. I even do keep images of the OS in the pool for reference,
history or for having the option to rollback to it.
Ok, the thing with the UIDs is going to be useful, as i maintain those
manually uptil now.
The only step, i am refusing to take is the replacing of SSD's (I
couldnt do that on my own and would require assistance always.) Thus i
prefer to multi-boot, which is fine, as long, as you know, what you are
doing and keep most of its config static, which i do.
Also, i did avoid SMR since years, and i have no need for samba at all.
Everything is local (or local to a vm). I was using a fast SSD for ZFS,
but theat one got consumed due to all the IO from the cache device. Now,
i opted for large enough RAM, which gives even better performance.
As you can see, we are almost on the same page, and i might add: i am
enjoying that a lot!
Am 27.03.2022 um 04:01 schrieb David Christensen:
>
> I suggest that you get an entry-level server. Install a small SSD. Do
> a fresh install of your server OS of choice. Use the recommended
> filesystem -- e.g. ext4 on Debian. Do not create an unprivileged user
> account during installation; or create a generic account if required
> (e.g. "debian"). Enable SSH service. Add site users and groups with
> planned UID's and GID's.
>
>
> Get an external HDD and take a raw binary image of the OS drive. Create
> a checksum file for the image file. Repeat periodically and as needed.
>
>
> Install two large HDD's (avoid SMR). Create a ZFS mirror. Install
> zfs-auto-snapshot and create cron job. Consider enabling default
> compression (lz4). Avoid deduplication. Consider adding a fast SSD as
> a cache device.
>
>
> Choose a networked version control system (I use CVS). Create a ZFS
> filesystem for the repository. Enable service and connect to
> repository. Install client. Check in your modified OS configuration
> files and any working files you maintain.
>
>
> Create a ZFS filesystem for Samba data. Enable Samba service and share
> filesystem. Avoid NFS. Collect and organize all of your data.
>
>
> Get two or more large external HDD's and implement backups in rotation.
>
>
> Archive important images and/or backups periodically and as needed.
>
>
> Finally, remove the OS drive in your existing computer. Install a blank
> SSD. Do a fresh install of your desktop OS of choice. If you want more
> than one OS, repeat with another blank SSD; e.g. avoid multi-boot.
> Install SSH client. Install version control system client. Create
> users, groups, UID's, and GID's to match server. Mount the Samba data
> share in a local directory. Add computer to image, backup, and archive
> procedures.
>
>
> David
Reply to: