HomeLab Development Board (ARM64) [PVE]: Backup and Restore for Win, Linux, and More

NO.1

Final Result

Previously installed pve7 on the Orange Pi 5 Plus and several systems.

Now attempting to backup and restore to the Raspberry Pi 5’s pve8 (essentially both are arm pve, just with different configurations).

<<HomeLab Development Board (ARM64) [PVE]: Installing Ubuntu Server 22.04 VM on PVE7>>

<<HomeLab Development Board (ARM64) [PVE]: Using Windows 11 on PVE7>>

<<HomeLab Development Board (ARM64) [PVE]: Installing OpenWrt>>

<<HomeLab Development Board (ARM64) [PVE]: Installing Kali Linux>>

PVE8 Overview

Restoring 4 systems, the 128GB disk space is nearly full, only 20GB remaining.

NO.2

Raspberry Pi 5 PVE

Windows 11 (ARM64)

Operations are relatively sluggish, starting Chrome browser is slow.

However, once the browser is launched, web browsing is less laggy, and basic browsing is fine.

Suitable for some visualization scripts or QQ online, etc.

Unless in a specified Windows scenario, other operations can be performed on the Raspberry Pi 5 OS desktop system’s Chrome browser, which is much smoother.

Kali Linux

Not usually needed, just to verify system installation feasibility.

Any system using Linux runs relatively smoothly, opening browsers and other applications without pressure.

Still, unless specified for Windows, it is recommended to use Raspberry Pi 5 OS or other lightweight Linux systems for web browsing or light office work.

OpenWrt

Basic gateway, minor adjustments made to the network interface, OpenWrt terminal is usable internally.

In the future, plan to connect a USB wired network card to the Raspberry Pi USB 3.0, which can serve as the LAN port for OpenWrt, outputting the network.

Can serve as a portable device.

Or connect a USB network card as a temporary network hotspot, providing basic network environment.

Multiple OpenWrt virtual machines can be set up.

One specifically for outputting USB limited network card LAN.

One specifically for receiving wireless WiFi with USB network card and generating AP hotspot.

Currently, the Raspberry Pi 5’s 2 USB 3.0 ports meet gigabit network environment; unless there are special needs, USB 2.0 as a hundred-megabit network port is also necessary for temporary emergency use.

Ubuntu Server 22.04 ARM64

Most commonly used is still the Ubuntu server environment.

Setting up Docker can deploy:

• Lightweight development environment (prototyping, project management, UI, code, testing, operations, database, etc.)

• Basic audio-visual (jellyfin media, audiobooks, library, music library, game library, comic library, etc.)

• Other daily applications (WizNote, lightweight cloud storage, drawing, hand-drawing, image compression tools, etc.)

NO.3

Other Systems

Ubuntu Desktop and Debian systems, similar to Ubuntu Server.

Installation and usage are fine, but due to insufficient disk space and non-essential systems, no installation testing will be conducted.

The Raspberry Pi series can serve entirely as OpenWrt gateways, NextCloud storage, Home Assistant smart home systems, etc.

Home Assistant will be deployed separately to a virtual machine on PVE later (not via Docker, requires complete content, such as HA’s built-in app store).

NO.4

Tips

Some thoughts

Need to quickly configure the pve management panel without a display when moving the Raspberry Pi’s location and network environment, such as specifying a static IP.

This means that pve configuration can be modified via SSH at any time to make the new network effective.

Currently, the Raspberry Pi 5 desktop is already connected to a WiFi network by default, expecting that in the future, without plugging in the network cable on pve,

The Raspberry Pi 5 will configure frp ssh, setting the mobile hotspot to the WiFi the Raspberry Pi 5 has connected to, then the computer can SSH into the Raspberry Pi to modify pve configurations.

When going out, taking the Raspberry Pi 5 as a gateway similarly, without inserting the network cable,

the phone shares a specified WiFi hotspot, OpenWrt virtual machine receives WiFi through the USB network card, then simultaneously shares a new WiFi hotspot through the USB network card, or outputs LAN through the USB wired network card, allowing the computer to receive the new WiFi or cable, using its own OpenWrt environment.

Ensure there will be no DNS pollution and other network issues.

At home, place a commonly used Home Assistant smart home setup.

Deploy MQTT and other gateway services through Linux services, and control smart devices at home through HA OS.

Ensure that in the event of power outages or internet disconnections, the smart home devices in the room and the internal network remain usable, with power banks providing continuous power, etc.

Currently, the settings for Raspberry Pi 5 are all on the TF card and are in testing.

If the results are good, I will try to use similarly sized, better-performing, lower-power ARM boxes to run.

For example, Orange Pi 3B, Orange Pi 5 Plus, both currently support SSD solid-state disks natively, so there’s no need to worry about data corruption and speed issues.

END.

Send the keywordJoin Group, to join the discussion group.

If you find this article helpful, pleaselike and bookmark, see you next time.

Recommended Reading

<<HomeLab Development Board (ARM64) [PVE]: Initializing Raspberry Pi 5 Desktop OS + aaPanel + pve8>>

☕ Friends, if you’ve read this far, are you sure you won’t follow along? 👇