#Proxmox Backup Server

[veuhoffblog]

Proxmox Backup Server (PBS) Upgrade: Eine Aktualisierung von 2.4 auf 3.0 durchführen

Vor wenigen Tagen, am 28. Juni 2023, ist die Version 3.0 vom Proxmox Backup Server (PBS) veröffentlicht worden. In dieser Anleitung zeige ich euch, wie sich der Server auf die neue Version upgraden lässt. Ein Tutorial darüber, wie ihr in wenigen Schritten einen Server mit Proxmox-VE...[Weiterlesen]

[virtualizationhowto]

Proxmox Backup Server: Ultimate Install, Backup, and Restore Guide

Proxmox Backup Server: Ultimate Install, Backup, and Restore Guide #proxmox #proxmoxbackup #proxmoxbackupserver #PVEbackup #dataprotectionproxmox #virtualizationhowto #homelab #selfhosted #VMbackup #containerbackup #disasterrecovery #ultimateDRguide

Backups are essential to running Proxmox VE in the home lab or production to avoid data loss. Proxmox Backup Server is a free solution to back up and recover Proxmox VE VMs and containers.  Table of contentsWhat is Proxmox Backup Server?Proxmox Backup Server featuresProxmox Backup Server installation step-by-step instructionsLogging into the Proxmox Backup client interfaceAdding a datastore for…

[techdirectarchive]

How to Deploy and integrate VHR with VBR

OOTBI (Object First Out-Of-the-Box Immutability) is an alternative solution to Veeam Linux Hardened Repository (VHR). Since I have covered OOTBI extensively in the past, I will now focus on VHR. Please, see Best Storage for Veeam: Comparing OOTBI by ObjectFirst to VHR. Therefore, in this article, we shall be discussing how to deploy and integrate VHR with VBR. Also, see Create a bootable USB on…

[rootresident]

Self Hosting

I haven't posted here in quite a while, but the last year+ for me has been a journey of learning a lot of new things. This is a kind of 'state-of-things' post about what I've been up to for the last year.

I put together a small home lab with 3 HP EliteDesk SFF PCs, an old gaming desktop running an i7-6700k, and my new gaming desktop running an i7-11700k and an RTX-3080 Ti.

"Using your gaming desktop as a server?" Yep, sure am! It's running Unraid with ~7TB of storage, and I'm passing the GPU through to a Windows VM for gaming. I use Sunshine/Moonlight to stream from the VM to my laptop in order to play games, though I've definitely been playing games a lot less...

On to the good stuff: I have 3 Proxmox nodes in a cluster, running the majority of my services. Jellyfin, Audiobookshelf, Calibre Web Automated, etc. are all running on Unraid to have direct access to the media library on the array. All told there's 23 docker containers running on Unraid, most of which are media management and streaming services. Across my lab, I have a whopping 57 containers running. Some of them are for things like monitoring which I wouldn't really count, but hey I'm not going to bother taking an effort to count properly.

The Proxmox nodes each have a VM for docker which I'm managing with Portainer, though that may change at some point as Komodo has caught my eye as a potential replacement.

All the VMs and LXC containers on Proxmox get backed up daily and stored on the array, and physical hosts are backed up with Kopia and also stored on the array. I haven't quite figured out backups for the main storage array yet (redundancy != backups), because cloud solutions are kind of expensive.

You might be wondering what I'm doing with all this, and the answer is not a whole lot. I make some things available for my private discord server to take advantage of, the main thing being game servers for Minecraft, Valheim, and a few others. For all that stuff I have to try and do things mostly the right way, so I have users managed in Authentik and all my other stuff connects to that. I've also written some small things here and there to automate tasks around the lab, like SSL certs which I might make a separate post on, and custom dashboard to view and start the various game servers I host. Otherwise it's really just a few things here and there to make my life a bit nicer, like RSSHub to collect all my favorite art accounts in one place (fuck you Instagram, piece of shit).

It's hard to go into detail on a whim like this so I may break it down better in the future, but assuming I keep posting here everything will probably be related to my lab. As it's grown it's definitely forced me to be more organized, and I promise I'm thinking about considering maybe working on documentation for everything. Bookstack is nice for that, I'm just lazy. One day I might even make a network map...

[techav]

If It's a Hack and It Works, Is It Really a Hack?

I have a couple servers at home — one running Proxmox VE and one running Proxmox Backup. I use the VM server when I need to spin up a development environment, for running the odd game server, serving files locally, running Home Assistant, etc. I also like to donate spare cycles to Folding@Home. The backup server of course is in case I do something stupid on the VM server.

There's just one problem with that. My second-hand 8-year-old dual-Xeon server runs hot.

It was too much to keep running in my home office. Between the two servers, my desktop, and my work laptop, I was regularly seeing ambient temperatures around 26°C. It was just too warm for comfort.

Last summer I moved my network gear and the two servers into the front coat closet. This was great for me working in my home office, but not so great for my servers. Despite adding a passthrough vent to the closet door and a vent fan to the ceiling, the closet was still consistently in the 26°-30°C range.

The ideal solution would probably be to use an enclosed server rack and run an exhaust vent up from the top. Unfortunately, rack-mount server cases are expensive, enclosed racks are very expensive, and my closet is too small for that anyway.

So I hacked together a solution.

I built a frame out of some cheap 1x2 lumber and wrapped a piece of thin sheet steel around the sides to make a crude plenum. On top, I added a 10x6 register box with a semirigid vent hose coming out of it. This gives me a guide for drawing air out of the servers and guiding it up to the vent fan in the ceiling.

To help things along, I added a 120mm fan inside the register box. But not some whisper-quiet Noctua. This is (if the Amazon listing is to be believed) a 5000 RPM, 210 CFM monster of a fan. It's loud, but moves a lot of air.

Too loud in fact. Its droning could not be silenced by any mere closet door. I had to add a PWM fan speed controller to calm it down. It's a cheap unit from Amazon, but it came with a temperature probe and it has a configurable operating range.

The result? Where previously the entire closet was consistently above 26°C, now it's staying around 23°. There is a difference of 5°C between ambient in the closet and the air inside the exhaust duct, so it is doing its job of redirecting the hot air from the servers.

I call that a successful hack.

[geekforcedotcom]

SysAdmin Sunday

One of my ProxMox hypervisor machines has a failing disk. Of course, it's the disk that stores the root filesystem of my homelab DNS server.

remediated by pulling a backup of running Pi-hole and restoring to the other hypervisor, running from an NVME drive now.

The best thing about running a Pi-hole, besides the whole house ad blocking thing, is the skinnable interface.

[cyber-security-tips]

How to Back Up Proxmox Virtual Machines

Proxmox VE is an open-source virtualization solution that combines two technologies: KVM and LXC. This provides virtualization and containerization capabilities for Windows and Linux-based servers.

You can perform Proxmox VM and data backups using different methods. Read here to check these methods.

[differenttimemachinecrusade]

Embedded Hypervisor Market Size, Share, Scope, Future Trends, Analysis, Forecast, Growth, and Industry Report 2032

The Embedded Hypervisor Market Size was valued at USD 12.02 Billion in 2023. It is expected to grow to USD 23.63 Billion by 2032 and grow at a CAGR of 7.80% over the forecast period of 2024-2032.

The Embedded Hypervisor Market is witnessing rapid growth due to the rising demand for virtualization, security, and real-time operating system integration. Industries such as automotive, aerospace, industrial automation, and healthcare are increasingly adopting embedded hypervisors to optimize performance and security. Advancements in AI, IoT, and 5G technologies are further driving market expansion.

The Embedded Hypervisor Market continues to evolve as companies focus on enhancing system efficiency, reducing hardware dependencies, and improving cybersecurity. With the proliferation of connected devices, embedded hypervisors are playing a crucial role in enabling secure multi-OS environments while maintaining real-time processing capabilities. As the demand for high-performance embedded systems increases, the market is expected to witness sustained growth.

Get Sample Copy of This Report: https://www.snsinsider.com/sample-request/3932 

Market Keyplayers:

VMware, Inc. (VMware vSphere, VMware Workstation)

TenAsys Corporation (INTEGRITY RTOS, iRMX Real-Time Operating System)

IBM Corporation (IBM PowerVM, IBM z/VM)

Siemens EDA (Mentor Embedded Hypervisor, Veloce Emulation Platform)

QNX Software Systems Limited (QNX Neutrino RTOS, QNX Hypervisor)

WindRiver Systems, Inc. (VxWorks, Wind River Linux)

SYSGO AG (PikeOS, ELinOS Linux)

ENEA (Enea OSE, Enea Linux)

Lynx Software Technologies, Inc. (LynxOS, LynxSecure)

Acontis Technologies GmbH (Xenomai, EtherCAT Master)

Citrix Systems, Inc. (Citrix Hypervisor, Citrix Virtual Apps and Desktops)

Proxmox Server Solutions GmbH (Proxmox Virtual Environment, Proxmox Backup Server)

Microsoft Corporation (Hyper-V, Windows Server)

Green Hills Software (INTEGRITY RTOS, MULTI IDE)

Sierraware (Sierra Hypervisor, Sierra Secure Virtualization)

Acontis Technologies GmbH (Xenomai, EtherCAT Master)

KUKA AG (KUKA.Safe Operation, KUKA.System Software)

Red Hat, Inc. (Red Hat Enterprise Linux, Red Hat Virtualization)

Fujitsu Limited (Fujitsu Cloud Hypervisor, Fujitsu Virtualization Platform)

Aricent (now part of Altran) (Virtualization Solutions, Embedded Software Solutions)

Market Trends Driving Growth

1. Increasing Demand for Secure Virtualization

With the rise of cyber threats, embedded hypervisors are gaining traction as they provide hardware-level isolation and secure OS partitioning.

2. Adoption in Automotive and Aerospace

The growing use of hypervisors in autonomous vehicles, avionics, and mission-critical applications is fueling market expansion.

3. Integration with AI and IoT

Embedded hypervisors are enabling real-time AI processing and IoT connectivity, enhancing smart system capabilities.

4. Shift Towards Open-Source Solutions

The adoption of open-source hypervisors is increasing due to cost-effectiveness and flexibility in customization.

Enquiry of This Report: https://www.snsinsider.com/enquiry/3932 

Market Segmentation:

By Component

Services

Software

By Enterprise Size

Small & Medium Enterprises (SMEs)

Large Enterprises

By Technology

Desktop Virtualization

Server Virtualization

Data Center Virtualization

By Application

IT & Telecommunications

Automotive

Aerospace & Defense

Industrial

Transportation

Market Analysis

Growing Demand in Automotive & Industrial Automation: The rise of autonomous systems and Industry 4.0 is boosting hypervisor adoption.

Increasing Regulatory Compliance: Strict security and safety regulations in industries such as healthcare and aerospace are driving innovation.

Expansion of Edge Computing: Hypervisors are playing a key role in edge computing by enabling secure, multi-OS execution.

Competition Among Key Players: Companies like VMware, Wind River, and SYSGO are investing in R&D to enhance hypervisor capabilities.

Future Prospects

The Embedded Hypervisor Market is set for significant expansion, with increasing investments in AI-driven automation, cybersecurity enhancements, and cloud-integrated virtualization. Emerging applications in medical devices, defense systems, and industrial robotics will further contribute to market growth. As organizations focus on optimizing embedded computing environments, the demand for hypervisors will continue to rise.

with sports teams and leagues to increase brand visibility and credibility.

Access Complete Report: https://www.snsinsider.com/reports/embedded-hypervisor-market-3932 

Conclusion

The Embedded Hypervisor Market is on a robust growth trajectory, driven by technological advancements, security needs, and real-time processing requirements. Companies investing in virtualization solutions, open-source innovations, and AI-powered embedded systems will shape the future of this evolving industry. With ongoing research and development, the market is poised to revolutionize secure and efficient embedded computing across various sectors.

About Us:

SNS Insider is one of the leading market research and consulting agencies that dominates the market research industry globally. Our company's aim is to give clients the knowledge they require in order to function in changing circumstances. In order to give you current, accurate market data, consumer insights, and opinions so that you can make decisions with confidence, we employ a variety of techniques, including surveys, video talks, and focus groups around the world.

Contact Us:

Jagney Dave - Vice President of Client Engagement

Phone: +1-315 636 4242 (US) | +44- 20 3290 5010 (UK)

[lowendbox]

Running your own infrastructure can be empowering. Whether you're managing a SaaS side project, self-hosting your favorite tools like Nextcloud or Uptime Kuma, running a game server, or just learning by doing, owning your stack gives you full control and flexibility. But it also comes with a cost. The good news? That cost doesn’t have to be high. One of the core values of the LowEndBox community is getting the most out of every dollar. Many of our readers are developers, sysadmins, hobbyists, or small businesses trying to stretch limited infrastructure budgets. That’s why self-hosting is so popular here—it’s customizable, private, and with the right strategy, surprisingly affordable. In this article, we’ll walk through seven practical ways to reduce your self-hosting costs. Whether you’re just starting out or already managing multiple VPSes, these tactics will help you trim your expenses without sacrificing performance or reliability. These aren't just random tips, they’re based on real-world strategies we see in action across the LowEndBox and LowEndTalk communities every day. 1. Use Spot or Preemptible Instances for Non-Critical Workloads Some providers offer deep discounts on “spot” instances, VPSes or cloud servers that can be reclaimed at any time. These are perfect for bursty workloads, short-term batch jobs, or backup processing where uptime isn’t mission-critical. Providers like Oracle Cloud and even some on the LowEndBox VPS deals page offer cost-effective servers that can be used this way. 2. Consolidate with Docker or Lightweight VMs Instead of spinning up multiple VPS instances, try consolidating services using containers or lightweight VMs (like those on Proxmox, LXC, or KVM). You’ll pay for fewer VPSes and get better performance by optimizing your resources. Tools like Docker Compose or Portainer make it easy to manage your stack efficiently. 3. Deploy to Cheaper Regions Server pricing often varies based on data center location. Consider moving your workloads to lower-cost regions like Eastern Europe, Southeast Asia, or Midwest US cities. Just make sure latency still meets your needs. LowEndBox regularly features hosts offering ultra-affordable plans in these locations. 4. Pay Annually When It Makes Sense Some providers offer steep discounts for annual or multi-year plans, sometimes as much as 30–50% compared to monthly billing. If your project is long-term, this can be a great way to save. Before you commit, check if the provider is reputable. User reviews on LowEndTalk can help you make a smart call. 5. Take Advantage of Free Tiers You’d be surprised how far you can go on free infrastructure these days. Services like: Cloudflare Tunnels (free remote access to local servers) Oracle Cloud Free Tier (includes 4 vCPUs and 24GB RAM!) GitHub Actions for automation Hetzner’s free DNS or Backblaze’s generous free storage Combined with a $3–$5 VPS, these tools can power an entire workflow on a shoestring budget. 6. Monitor Idle Resources It’s easy to let unused servers pile up. Get into the habit of monitoring resource usage and cleaning house monthly. If a VPS is sitting idle, shut it down or consolidate it. Tools like Netdata, Grafana + Prometheus, or even htop and ncdu can help you track usage and trim the fat. 7. Watch LowEndBox for Deals (Seriously) This isn’t just self-promo, it’s reality, LowEndBox has been the global market leader in broadcasting great deals for our readers for years. Our team at LowEndBox digs up exclusive discounts, coupon codes, and budget-friendly hosting options from around the world every week. Whether it’s a $15/year NAT VPS, or a powerful GPU server for AI workloads under $70/month, we help you find the right provider at the right price. Bonus: we also post guides and how-tos to help you squeeze the most out of your stack. Final Thoughts Cutting costs doesn’t mean sacrificing quality. With the right mix of smart planning, efficient tooling, and a bit of deal hunting, you can run powerful, scalable infrastructure on a micro-budget. Got your own cost-saving tip? Share it with the community over at LowEndTalk! https://lowendbox.com/blog/1-vps-1-usd-vps-per-month/ https://lowendbox.com/blog/2-usd-vps-cheap-vps-under-2-month/ https://lowendbox.com/best-cheap-vps-hosting-updated-2020/ Read the full article

[mip248]

Airwaves (Or, how I learned to stop worrying and love the aircraft on my screen

Admittedly, I'm a bit of a fan of aviation. Most forms of transit actually, but that's for a different blog. I like aircraft. They've always fascinated me, and at a point, I'd wanted to get my pilots license.

I just think they're neat. I enjoy flying, I enjoy the intricacies of the taxiing, the take-off, the landing, and hopefully enjoying in-flight wi-fi in-between. I enjoy seeing and knowing the ins and outs of how I get from Point A to Point B via plane.

So what better way to enjoy two things at the same time, than by mixing my fascination of aviation with my passion for technology! I was shown this by a colleague at a past workplace, and I just HAD to have one myself. Below, I'll be chronicling my journey, experience, frustrations and wins with tracking aircraft in my area over ADSB.

Our adventures begin with this little nugget - I figured I'd start small and assuming all goes well, I'd scale up. Here's what it looked like initially

Not bad - just on 100nmi of range.

Once I moved to this arrangement, I was getting no more than 25nmi to the south, but got over 100nmi to the north, which was a pleasant boost, no doubt helped by the wall.

I invested in a RadarBox ADS-B FlightStick and the associated dipole antenna.

25nmi to the south, and more than 135nmi to the north. A sound improvement, but we can do better!

And it starts with the roof!

Much improved coverage all-round! 107nmi to the west, 162nmi to the east and north, and around 80nmi to the south. The Pi was in the roof, running off a POE Spliter

This is where I begin to have issues though.

POE Splitter burn-outs

SD Card corruptions

The Airnav stick not being recognised

So I get through the POE Splitter burnouts by getting another one. I get another ~2-4 weeks out of that one. Then the SD Card dies. I swap it over and get about 2 months. Then it dies. Amongst this, the Airnav stick is being less than helpful and is not consistently picked up by the Pi.

Not good.

So where to from here? I saw a few options:

Try and have the Pi network boot the ADSB feeder image from a server

Get another SD card and go again

Try USB over Cat 6 converters and do it that way

Install an Active USB Extension cable

Option 2 was the last option - I really didn't want to go down this route because it's just me purchasing SD cards again and again and restoring backups and I have better things to do.

Option 1 was the first idea - it keeps the power and network up near the AirNav stick and is what I experimented with first.

I found that I was not able to get much love with that - mostly involved with trying to get rootFS off the SD card was painful and difficult and was abandoned after a weekend.

This led me to option 3 - try some USB over Cat converters and give that a go. I'll virtualise the ADSB receiver as a VM in ProxMox and do it that way. And I did - I picked up these promising DOSS USBCAT100 dongles, which on the product page spec sheet advise that USB 2.0 full power/speed can be done up to 50 metres. They arrived, yay, happy days! I thought "before I get up in the roof and use these and find out they may not work, I better test these", and so I did, with my iPhone and a 1.5 metre Cat 6 cable only to see...

Wonderful. It's USB 1.1 speeds. Not great. The common consensus if you look up USB speeds and RTLSDR sticks is that they need USB 2.0 speeds, so this can't be used, and I had to get a return.

So I went for option 4 - a 15M Active USB Extension Cable from 4Cabling. I got up in the roof and ran that cable from the rack to the spot, plugged the AirNav stick in and connected the server and... Something...ISH? The stick fired up, but the light on the stick was flickering, and the data activity lights on the USB cable were not consistent either. Eventually both got settled and off we went.

Off we went to not too much luck. Every 2-6 hours, the stick would fail/stop and not be recognisable by the host.. How annoying... No mix of USB 2.0 or USB 3.0 ports would work. Rebooting the ProxMox host didn't yield any wins - I had to shutdown and power on every time this happened. Thinking it may be power related, I got one of those USB splitter cables that shipped with many external HDDs of yore (pre-USB 3.0 days) to see if that would make a difference.

And it did, again briefly. No mix of 2.0 or 3.0 ports worked, but I DID have some better luck with using a USB power bank on the power-only cable, but that failed again (just after a longer time period), and so did using an Apple 10W USB Power Brick. A 12W Apple Power Brick also didn't work.

So, now with seemingly nothing else to try, I went with a FlightAware Pro Stick Plus. It's been installed for over a week now and is happily plodding away! I'm getting coverage of more than 200nmi north, getting around 175nmi east, more than 100nmi south, and 125nmi west. The amount of hits is also much more consistent.

For reference, for my aircraft tracking, I use adsb.im to track and feed. Make sure you take backups early and often!

[virtualizationhowto]

NAKIVO Proxmox Backup in v10.11 New Features

NAKIVO Proxmox Backup in v10.11 New Features @nakivo #proxmox #nakivo #proxmoxbackup #proxmoxbackupserver #commercialproxmoxbackup #nakivo1011 #backup #disasterrecovery #replication #321backup #virtualization #homeserver #homelab #vhtforums

Well, in a move that makes it one of the first (if not THE first) commercial backup vendor to offer support for Proxmox Backup and data protection, NAKIVO Backup & Replication v10.11 indeed adds just that, including other new features in this release. Let’s see why this is important with the massive demand from companies for the Proxmox VE hypervisor due to the news of the VMware by Broadcom…

[emacs-unofficial]

For storage, get a NAS. Either prebuilt (e.g synology) or build something yourself using truenad.

Prebuilt has the advantage that they most likely use very energy efficient parts that are hard to aquire or hard to work with for DYI builds.

For offsite backup, the cheapest would be to have a friend with some storage and use each others systems as offsite storage.

If that is not an option, try to get some cheap hosted S3 storage. Amazon has the lowest running cost with their longterm/archival solutions, but they come with the downside of steep transfer costs once you need to get to your data. Other people recommend backblaze. I'm personally using Wasabi.

Software wise, there is a lot good software to choose from. What exactly you want to use depends on your usecase.

Dirvish if you want to let a backup server pull the data instead of pushing from the source

duplicity is what I'm currently using to backup my VPS to S3 Storage

restic as an alternative for duplicity

Déjà Dup for a nice GUI app for the desktop (based on duplicity or restic)

If you backup windows and don't mind the software not being open source, I really recommend veeam free. Just works rock solidly.

honorable mentions: rclone, syncthing (not really a backup), whatever is built in to what you use (e.g. proxmox backup settings, Synology Hyperbackup, etc.)

Most importantly, remember the 3-2-1 Principle

you should have 3 copies of your data (your production data and 2 backup copies) on two different media with one copy off-site for disaster recovery.

Pulled a sneaky on my co-worker today :p

[webyildiz]

Proxmox is an open-source server virtualization platform that allows you to manage and deploy virtual machines and containers. It is based on Debian and provides a powerful web-based graphical interface for easy management. Here's an ultimate guide on how to install and configure Proxmox: [tie_index]System Requirements[/tie_index] [padding top="0" bottom="0" right="5%" left="5%"] System Requirements: A dedicated physical machine or server. Sufficient CPU, RAM, and storage resources for your virtualization needs. Compatible hardware for virtualization (CPU with Intel VT or AMD-V support).  [tie_index]Installation[/tie_index] [padding top="0" bottom="0" right="5%" left="5%"] Installation: Download the Proxmox VE ISO image from the Proxmox website (https://www.proxmox.com/downloads). Create a bootable USB or burn the ISO to a DVD. Boot your server from the USB or DVD. Follow the on-screen instructions to install Proxmox VE. Choose a suitable installation option, such as wiping the entire disk or installing alongside an existing operating system. Set a root password and configure the network settings.  [tie_index]Initial Configuration[/tie_index] [padding top="0" bottom="0" right="5%" left="5%"] Initial Configuration: After installation, access the Proxmox web interface by opening a web browser and entering the IP address of your Proxmox server (https://:8006). Accept the self-signed SSL certificate warning (or install a trusted SSL certificate). Log in using the root username and the password you set during installation.  [tie_index]Network Configuration[/tie_index] [padding top="0" bottom="0" right="5%" left="5%"] Network Configuration: Configure your network interfaces by going to "Datacenter" in the left-hand menu and selecting "Network" in the top menu. Edit the "vmbr0" interface to match your network settings, such as IP address, subnet mask, gateway, and DNS servers.  [tie_index]Storage Configuration[/tie_index] [padding top="0" bottom="0" right="5%" left="5%"] Storage Configuration: Proxmox uses different storage types, including local storage, iSCSI, NFS, and Ceph. Choose the appropriate storage type based on your requirements. To add storage, go to "Datacenter" and select "Storage" in the top menu. Click "Add" and follow the wizard to configure the storage type, path, and other relevant settings.  [tie_index]Create Virtual Machines (VMs)[/tie_index] [padding top="0" bottom="0" right="5%" left="5%"] Create Virtual Machines (VMs): Click on "Create VM" in the top menu to start the VM creation wizard. Select the desired options, such as VM ID, name, guest OS, CPU, RAM, and disk size. Choose the storage location for the VM disk. Configure the network settings for the VM. Complete the wizard, and the VM will be created.  [tie_index]Additional Configuration[/tie_index] [padding top="0" bottom="0" right="5%" left="5%"] Additional Configuration: Proxmox offers many advanced features, such as high availability (HA), clustering, and backups. Explore the Proxmox documentation for more details on these features and how to configure them based on your requirements. Remember to regularly update your Proxmox installation by applying the latest updates and security patches. Please note that this is a general guide, and the steps may vary based on the specific version of Proxmox you are using. Always refer to the official Proxmox documentation for detailed instructions and the most up-to-date information.

[veuhoffblog]

Proxmox Backup Server: Wie Backups eingerichtet werden

Im vorherigen Artikel haben wir gemeinsam einen Proxmox Backup Server installiert. Dieser Beitrag baut auf dem anderen auf und ist so gesehen die Fortsetzung. Ich erkläre euch die wichtigsten Schritte und Einstellungen, die direkt nach der Installation und Inbetriebnahme...[Weiterlesen]

[emacs-unofficial]

My Linux configs are in a git repo with my server as remote. All important digital files are edited online (currently using google docs but looking into switching to a selfhosted alternative) or stored on my paperless-ngx server.

My Servers gets backed up daily to an S3 storage I rent. Files only for my docker-compose based setup on a VPS and disk drives for my proxmox homelab.

Testing my homelab backup is still on my todo list tho...

I decided to check my storage and noticed I had like 70 gigs more than I expected, even though the last major memory change I remembered doing was installing a 25+ gigabyte game

Then I remembered that I moved my backups to a USB and I haven't backed up my system in months and also have been making notable changes to how I use it

So yeah, I'm backing stuff up as I write this

[computingpostcom]

The Network File System (NFS) is a well-proven, widely-supported and standardized network protocol used to share files between separate computer systems. The Network Information Service (NIS) is commonly used to provide centralized user management in the network. When NFS is combined with NIS, you’re able to have file and directory permissions for access control in the network. The default configuration of NFS is to completely trust the network and any machine connected to a trusted network is able to access any files that the server makes available. In Proxmox Virtualization Environment you can use local directories or locally mounted shares for storage. A directory is a file level storage that can be used to store content type like containers, virtual disk images, ISO images, templates, or backup files. In this post we discuss how you can configure NFS share on Proxmox VE for ISO images. The same process applies for any other storage purpose like storage of virtual disk images and templates. In Proxmox VE, storage configurations are located in the file /etc/pve/storage.cfg. You can list contents in /var/lib/vz/ directory: $ ls /var/lib/vz/ dump images template Within templates directory we can see iso and cache sub-directories. $ ls /var/lib/vz/template/ cache iso The table below shows a predefined directory layout to store different content types into different sub-directories Content type Subdir VM images images// ISO images template/iso/ Container templates template/cache/ Backup files dump/ Snippets snippets/ Configure NFS server Share Login to the server that will act as NFS server and configure export for ISO contents. If you’re using a ready solution with NFS feature, you can skip this steps. Install NFS server package on your Linux system. ### RHEL Based systems ### sudo yum -y install nfs-utils sudo systemctl enable --now rpcbind nfs-server sudo firewall-cmd --add-service=nfs --permanent sudo firewall-cmd --reload #If use NFSv3 allow the following sudo firewall-cmd --add-service=nfs3,mountd,rpc-bind --permanent sudo firewall-cmd --reload ### Debian Based systems ### sudo apt -y install nfs-kernel-server Let’s now configure NFS export by editing the file below $ sudo vim /etc/exports /nfs/isos *(rw,no_root_squash,no_subtree_check) In the example we’re setting /nfs/isos as NFS share for ISO images on Proxmox VE. Confirm it works after the changes by re-exporting shares: $ sudo exportfs -rrv exporting *:/nfs/isos Mount NFS ISO share on Proxmox VE server Install NFS utility packages in your Debian / Ubuntu system. sudo apt -y install nfs-common Our NFS server setup is: NFS Server IP address: 172.20.30.3 ISO Export path on NFS Server: /nfs/isos Ensure you don’t have any data inside isos directory: ls /var/lib/vz/template/iso/ On Proxmox VE, which acts as NFS client, execute the following to display RPC information of the remote NFS server. $ rpcinfo -p 172.20.30.3 program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100005 1 udp 20048 mountd 100005 1 tcp 20048 mountd 100005 2 udp 20048 mountd 100005 2 tcp 20048 mountd 100024 1 udp 46068 status 100024 1 tcp 43599 status 100005 3 udp 20048 mountd 100005 3 tcp 20048 mountd 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 100003 3 udp 2049 nfs 100227 3 udp 2049 100021 1 udp 44453 nlockmgr 100021 3 udp 44453 nlockmgr 100021 4 udp 44453 nlockmgr 100021 1 tcp 35393 nlockmgr 100021 3 tcp 35393 nlockmgr 100021 4 tcp 35393 nlockmgr

Run the showmount to display all active folder exports in an NFS server: $ showmount -e 172.20.30.3 Export list for 172.20.30.3: /nfs/isos * Option 1: Configure mount using Proxmox pvesm (Recommended) pvesm is a powerful Proxmox VE Storage Manager command line tool. Use the tool to scan for NFS shares in the server we just configured. $ sudo pvesm scan nfs 172.20.30.3 /nfs/isos * We’re going to run commands shared below to configure NFS Storage for ISO images on our Proxmox environment. sudo pvesm add nfs NFS-iso --server 172.20.30.3 --path /var/lib/vz/template/iso/ --export /nfs/isos --content iso Where: 172.20.30.3 is the IP address of NFS server /nfs/isos is the path to the iso folder on NFS server (NFS export path) /var/lib/vz/template/iso/ path on Proxmox server where NFS share is mounted Listing contents of /etc/pve/storage.cfg after command execution. $ cat /etc/pve/storage.cfg dir: local path /var/lib/vz content iso,vztmpl,backup lvmthin: local-lvm thinpool data vgname pve content rootdir,images nfs: NFS-iso export /nfs/isos path /var/lib/vz/template/iso/ server 172.20.30.3 content iso We can confirm new lines were added to the file. With the df command you can check if mounting was successful. $ df -hT /var/lib/vz/template/iso Filesystem Type Size Used Avail Use% Mounted on 172.20.30.3:/nfs/isos nfs4 400G 39G 341G 11% /var/lib/vz/template/iso Option 2: Configure mount using /etc/fstab You can also use mount command for runtime testing if Proxmox server can access NFS server and exported directory. sudo mount -t nfs 172.20.30.3:/nfs/isos /var/lib/vz/template/iso/ To persist the configurations use /etc/fstab file. $ sudo vim /etc/fstab # Add NFS ISO share mount 172.20.30.3:/nfs/isos /var/lib/vz/template/iso nfs defaults 0 0 Unmount before testing: sudo umount /var/lib/vz/template/iso Validate mounting can be done successfully sudo mount /var/lib/vz/template/iso Check with the df command: $ df -hT /var/lib/vz/template/iso/ Filesystem Type Size Used Avail Use% Mounted on 172.20.30.3:/nfs/isos nfs4 400G 20G 360G 6% /var/lib/vz/template/iso Login to Proxmox Web dashboard and check the status of your mount We can see a list of images available on NFS share. From here VM installation with the ISOs can begin.