Best external SSD for Home Assistant and Proxmox backups

Your backup should survive the box it protects. An external SSD makes that simple: copy a recovery set, unplug it, and put it somewhere separate. The Samsung T7 Shield 2 TB is our all-round pick for Home Assistant exports and Proxmox backup archives. The SanDisk Extreme Portable SSD 2 TB is the alternative if you want a five-year limited warranty and an included USB-A adapter.

Both use a 10 Gbps USB connection. Neither needs a glamorous benchmark number to do this job: capacity, a working restore and a rotation you actually follow matter more.

Drive specifications come from the makers; backup instructions come from Home Assistant and Proxmox documentation.

The quick picks

• Most people: Samsung T7 Shield 2 TB. A rugged portable enclosure, 10 Gbps USB and enough room for the example backup sets below. Choose it for a drive you carry between your backup computer and a separate storage spot.
• Five-year warranty alternative: SanDisk Extreme 2 TB. The exact SDSSDE61-2T00-G25 model has the same published read/write ceiling, a longer limited warranty and a USB-A adapter in the box. That adapter is handy when your backup laptop and server have different sockets.
• Already have a healthy external drive? Use it. Make a fresh backup and restore something before replacing working hardware. For a spare bare SATA disk, our USB SATA dock guide offers a different route to removable backups. Still choosing between a hard drive and an SSD? Use the backup-job decision table to match the drive to your recovery set.

Compare the exact drives

Drive	Capacity	USB interface	Maker maximum read / write	Password encryption	Limited warranty
Samsung T7 Shield	2 TB	USB 3.2 Gen 2, 10 Gbps	1,050 / 1,000 MB/s	AES-256 hardware encryption, vendor software	3 years
SanDisk Extreme, SDSSDE61-2T00-G25	2 TB	USB 3.2 Gen 2	1,050 / 1,000 MB/s	AES-256 hardware encryption, vendor software	5 years

Those are Samsung’s datasheet figures and SanDisk’s exact-model specifications, not backup speeds measured here. The source, compression, USB port and workload all affect a real backup job.

Both makers list IP65 protection and up to three-metre drop resistance under their stated conditions. That’s useful for carrying a drive, not a reason to leave your only copy beside a leaking pipe. The extra warranty years on the SanDisk are a purchase term, not a recovery service for your files.

How much capacity do you need?

Start with the actual size of a completed backup, not the capacity printed on the server’s boot disk. Decide how many recovery points to keep, then leave room for the next backup before pruning older ones. Choosing a two-bay backup destination? Our DXP2800 vs DS225+ comparison covers the enclosure decision.

Here are explicit planning examples, using decimal GB. Assume each Home Assistant export is 8 GB, retain 14, and retain seven full Proxmox guest-backup sets. The guest sets below are hypothetical 60 GB or 120 GB totals after backup compression. We use 80% of nominal drive capacity as a planning ceiling, leaving space for growth and filesystem overhead.

Example	HA copies	Guest-backup copies	Total planned files	Fits within 800 GB planning space on 1 TB?	Fits within 1,600 GB on 2 TB?
Home Assistant only	8 GB × 14	None	112 GB	Yes	Yes
HA + small guest set	8 GB × 14	60 GB × 7	532 GB	Yes	Yes
HA + larger guest set	8 GB × 14	120 GB × 7	952 GB	No	Yes

For HA alone, a smaller existing drive may be plenty. For several VMs, the 2 TB picks give the larger example room to breathe. Replace the assumed sizes with your own completed files, including anything you copy alongside them. Deduplication savings from Proxmox Backup Server belong to a different calculation; don’t assume them for ordinary file archives.

USB-C is the plug; USB speed is the connection

Use the supplied data cable and a host port that supports the drive’s interface. A USB-C socket alone doesn’t tell you its speed, and a charging cable can be the wrong tool for moving a backup set.

A faster portable SSD won’t fix a slow source disk or a slower host connection. For this shortlist, a working 10 Gbps path is the target. Plug directly into the computer for the first backup and restore so you can establish a reliable baseline before adding docks and hubs.

Out of ports? A powered USB hub gives the SSD and other cables room, while the Zigbee stick keeps its own USB 2.0 spot.

If your main goal is an internal app or VM pool rather than a removable copy, use the NAS cache and app-pool SSD guide instead. A pocket SSD shines when you can unplug and rotate it.

For more local-control projects, start at the Home Assistant hub.

Home Assistant: export a backup onto the SSD

For a straightforward removable copy, attach the SSD to your computer, download the backup there, then copy it to the drive. This follows HA’s documented download workflow without turning your live HA data disk into your supposed backup.

1. Open Settings → System → Backups. Set up automatic backups if you haven’t already, and save the emergency kit somewhere separate from the HA host.
2. Select Show all backups. On the backup you want, open the three-dot menu and choose Download.
3. Choose an encrypted download when you want the exported archive to remain encrypted. HA normally decrypts a downloaded backup on the fly; an encrypted source backup doesn’t automatically mean the file in your Downloads folder is encrypted.
4. Copy the downloaded file onto the SSD. Keep its date clear, and keep the emergency kit accessible without that host.
5. Safely eject the drive after copying. Keep another copy away from this drive and computer.

The Home Assistant backup guide explains the download and restore paths. Its OS storage instructions also cover network storage with the Backup usage for an automated destination.

Moving HA’s data disk to USB moves the live data. It doesn’t create an independent offline copy. Pick that feature to expand working storage; pick an exported backup or a separate backup destination for recovery. If HA runs inside Proxmox, keep the HA-native export alongside the VM backup so you have both an application restore path and a whole-guest restore path.

Proxmox: regular archives or Backup Server?

Proxmox VE documents two different backup destinations: file-level storage holds regular backup files, while Proxmox Backup Server stores deduplicated chunks and metadata. Buying a USB SSD doesn’t turn directory backups into PBS.

For a removable archive drive, use a Linux-mounted filesystem and define Directory storage for that mount point, with backup content enabled. Proxmox’s directory-storage documentation supports Linux-mounted filesystems and requires POSIX-compatible storage. An ext4 filesystem is a straightforward Linux-only choice; formatting erases the selected drive, so identify it by capacity and device details first.

Make the storage unavailable when the SSD is absent. The storage-manager manual documents is_mountpoint: it considers externally mounted storage offline when the mount is missing. Set that guard for your backup storage rather than letting an empty mount directory become a destination on the host disk.

Then create a backup job targeting that storage and run it once while you can watch the result. For running VMs, snapshot mode keeps downtime low; a configured, running QEMU guest agent can freeze and thaw guest filesystems to improve consistency. Containers have different snapshot requirements, so use the documented mode for the guest type. Databases may also need their own application-aware dump.

For an established PBS installation, use its documented backup and datastore workflows. Don’t copy a handful of chunk files and call that a portable recovery set. PBS encryption, pruning and verification are system features to plan, not boxes on the SSD packaging.

Encryption: protect the backup, not just the enclosure

Hardware AES on the drive is useful only when you can unlock it on the machine that must restore it. Samsung lists its password software requirements for Windows, macOS and Android; SanDisk lists Windows/macOS requirements for its password protection. Neither source gives you a documented unattended Linux-unlock workflow for a Proxmox host.

For unattended backups, choose encryption at the backup layer and keep recovery keys separately. HA provides encrypted archives and its emergency kit. Proxmox Backup supports client-side AES-256-GCM encryption, with separate key handling. Ordinary directory archives need their own encryption plan; compression alone doesn’t encrypt them.

Endurance and the restore drill

The reviewed drive specifications don’t provide a numeric TBW rating to rank these two by write endurance. Use their stated warranties as warranty information, and size retention from your workload rather than borrowing a TBW figure from an unrelated internal SSD.

Before trusting your rotation:

• Restore an HA backup on a spare or temporary installation, keeping duplicate automations from operating real devices.
• Restore a Proxmox archive to a separate guest ID with an isolated network. Boot it and open the application or files you care about.
• Retrieve an encrypted copy using the separately stored key. A backup that needs a password trapped on the failed host is a puzzle you don’t want.
• Record the backup date, restore result and next rotation. Eject and disconnect the finished copy.

Keep the bigger plan in view with RAID, snapshots and backups, and use the SMART health guide for checks supported by your drive and USB bridge.

Want to choose or reuse the SSD inside? Our USB4 NVMe enclosure guide compares fanless and actively cooled cases, an older-port alternative and checksum verification for a NAS copy.

The verdict

Buy the T7 Shield 2 TB for a straightforward portable backup drive. Choose the SanDisk Extreme 2 TB for its five-year limited warranty and included USB-A adapter. Start with a completed backup, save the key separately, restore it once, then unplug the finished copy. That’s the useful upgrade: a recovery path that lives outside the machine you’re protecting.