I almost always use the native tools FlatPak is heavier and CAN have interaction problems with the OS and you are 100% dependent on the packager for updates.

APT relies on the OS components for patching and updates mostly. If the APT REPO is from the OS vendor, they maintain patching and compatibility for you. If a third party repo, the job is split between the OS vendor and the package manager.

And to make it really overkill and reliable, duplicate this physical installation twice more and setup DRBD and Pacemaker for an extremely HA filesystem with Quorum.

Like others have mentioned

www.xbyte.com is one choice.

The other one is:

www.savemyserver.com

I will stick to black and white printing to save costs. If a color printer is absolutely necessary, we can make it available for limited use..

As you know almost all drivers are a part of the kernel itself. There isn't a way to "export" them in the way that you're thinking -- at least not that I'm aware. If you installed a package that included a 3rd party hardware driver, perhaps you can just download the rpm or deb file from its repo to back it up. Some kernel modules (or groups of kernel modules) are the drivers for some hardware, and you could potentially backup those files to load later. I haven't had hardware that has required special kernel modules that would create that situation.

To be honest, if that system crashes, reinstalling your Linux distribution will be your method of getting drivers for your hardware :).

You can also try whois.sc

@IThomeboy80

I think I have already tried this and it didn’t work.
That said, I also may not have work ask thing I have tried.

When I got the 720, I also got a 710. The 720 had eight drives in it, but was given to a friend to host one of our games. Turns out those drives had windows 10 on them.

We dropped them in the 720 and it will boot, but still complains about the iDrac…

It’s been a bit crazy between a new roof, plumbing issues and rain from Helene. No damage to the house, but the an area has a lot of trees downed…. Nothing like this in NC or TN..

I will try again and see what happens

Well,.. with the weather we had rip through Kentucky this past week (TS / TD Helene) Didn't get to circle back to this, but discovered one possible issue. the Headset button on the phone itself needed to be enabled. (duh)

Yes, when I test this with another phone (T46p) and my Jabra headset, the headset doesn't ring when dialed. Checked to ensure that phone was enabled on the Jabra - but didn't seem to make a difference.

I expect it is something simple,.. and easy to overlook, but not found it yet. And today I am trying to not think about work and work on the 720,.. Curious as to what else I can end up putting on this as a Proxmox host.

@IThomeboy80 Thanks, I have only used Scale Clusters which is the close I have tried so yeah.

@gjacobse Most likely this is an SSH timeout. Might be on the client end. Is the timeout the same regardless of where you connect from? What if you connect via SSH instead of NX?

@gjacobse

We had something similar recently, with Server 2022 and Bartender server.
The printer had to be installed under the AD Service Account that the Bartender app is installed under, on that app server.

Then the calls to our print server, where the printer is pointed to in the app itself, worked properly. Otherwise, there would be a 3 min timeout before even the labels from the app would print.

So try to install it locally under the account that the SAP app was installed under.

Try to reset the printer, and the web server via the printers web gui if possible also.

Our issue was with the older Xi4's not the newer ZD621.
Our print server is Win Server 2022 Core.

@gjacobse said in ReadyNAS314: likely failing:

@DustinB3403 said in ReadyNAS314: likely failing:

@gjacobse said in ReadyNAS314: likely failing:

I do have a “backup” but, looks like it’s a month or so old.

This is where you screwed up...

You know what they say about people and glass houses?

Hey I'm sure I'll have my own issue at some point.

lol

@gjacobse glad I could help

Annnd- the printer is already working... not that THAT is any issues...

We have all APCs and they work fine in our DC. They work fine for us which include our windows and linux servers.

https://forum.proxmox.com/threads/setting-time-options.28099/

System time is generally viewed as UTC Time - which I can understand for standardization.
Will have to 'adjust' my expectations.

@gjacobse You should consider publishing this and others (sanitizing of course) to GitLab or GitHub. It can serve as a reference for you as well as a bit of a portfolio. I know for a fact my GitLab stuff had a positive effect with helping me land my current gig.