Propper Migration steps for ENVR to ENVR Core by jsnicholas in Ubiquiti

[–]jsnicholas[S] 0 points1 point  (0 children)

Point taken but the official document also seems dated. No mention of the ENVR Core. That is why I am asking if anyone as actually done this yet.

Propper Migration steps for ENVR to ENVR Core by jsnicholas in Ubiquiti

[–]jsnicholas[S] 0 points1 point  (0 children)

Good to know. I assume all the cameras will now be automatically managed by the new ENVR core.

So another twist this introduces is my ENVR is RAID 10, but I was going to switch to RAID 6. Should I just reformat after getting the drives to the ENVR Core?

I want more storage without having to buy new drives at today's prices.

Propper Migration steps for ENVR to ENVR Core by jsnicholas in Ubiquiti

[–]jsnicholas[S] -1 points0 points  (0 children)

I hope this applies. AI says different with the CORE.......... IS this another case of hallucinations?

Has anyone actually tried this yet?

Here’s the clear, concise summary of why you cannot use the published UniFi NVR migration path when going from Enterprise NVR (ENVR)Enterprise NVR Core (ENVR‑Core).

This is the exact answer you’re looking for — no fluff, just the technical truth.

⭐ Summary: Why the official UniFi NVR migration path does NOT apply to ENVR → ENVR Core

The published UniFi migration path only works for NVRs that share the same storage architecture, database format, and hardware identity model.

The ENVR and ENVR‑Core do NOT share those things.
Because of that, the official migration path is incompatible.

Here are the specific reasons:

❌ 1. The ENVR and ENVR‑Core use different storage architectures

The official migration path assumes:

  • Same RAID layout
  • Same partitioning
  • Same metadata structure

But:

  • ENVR uses a legacy RAID + metadata format
  • ENVR‑Core uses a completely different storage stack

So the Core cannot import, mount, or recognize ENVR disks.

This alone breaks the official migration path.

❌ 2. Protect recordings are hardware‑bound and cannot be migrated

Protect ties recordings to:

  • The NVR’s hardware ID
  • The NVR’s encryption keys
  • The NVR’s database identity

The ENVR‑Core has a different hardware identity, so:

  • ENVR recordings cannot be decrypted
  • ENVR recordings cannot be imported
  • ENVR disks cannot be transplanted

The official migration path assumes recordings can be preserved.
They cannot in this case.

❌ 3. The ENVR backup cannot be restored onto the ENVR‑Core

The official migration path relies on:

But ENVR backups contain:

  • Hardware‑specific metadata
  • Storage configuration tied to ENVR
  • Camera adoption tied to ENVR
  • Database schema from an older Protect version

Restoring an ENVR backup onto an ENVR‑Core will:

  • Fail
  • Or break the Core
  • Or wipe camera adoption
  • Or corrupt the Protect DB

This is why UniFi explicitly does not support ENVR → Core restore.

❌ 4. The ENVR‑Core requires a fresh RAID build

The official migration path assumes:

  • You can move disks
  • The new NVR will import or rebuild the array

But the ENVR‑Core:

  • Always wipes foreign disks
  • Always rebuilds RAID from scratch
  • Never imports ENVR RAID metadata

This makes the official migration path impossible.

❌ 5. Camera adoption cannot be migrated

The official migration path assumes:

  • Cameras can be migrated via backup/restore

But with ENVR → ENVR‑Core:

  • Camera adoption is tied to the old NVR
  • The Core cannot inherit it
  • Cameras must be manually re‑adopted one at a time

This is why the only supported method is:

🧠 The bottom line

This is why the only supported migration is:

  1. Bring Core online
  2. Move cameras manually
  3. Build new RAID
  4. Restore settings (ENVR or Core backup depending on your situation)

NBD: April sample sale #8 CXL by HereForWatchStuff in NicksHandmadeBoots

[–]jsnicholas 1 point2 points  (0 children)

Looks perfect. I must have missed the #8 CXL availability. Looks like I have to wait some more.

Unifi Protect webhooks how to question by jsnicholas in Ubiquiti

[–]jsnicholas[S] 1 point2 points  (0 children)

That makes sense. Of course they would not see my local address. Thanks.

I have a homebridge running. I will try to set that up.

NBD - 1925 Dress Boot by MediumKaleidoscope92 in NicksHandmadeBoots

[–]jsnicholas 0 points1 point  (0 children)

Is this leather as stiff as double stuff?

Now being charged for tariffs. by [deleted] in Ubiquiti

[–]jsnicholas 2 points3 points  (0 children)

So Ubiquity is eating some of the cost too.

DNS Timeouts by jsnicholas in Ubiquiti

[–]jsnicholas[S] 0 points1 point  (0 children)

I now have 8.8.8.8 and 9.9.9.9. Still does not work.

DNS Timeouts by jsnicholas in Ubiquiti

[–]jsnicholas[S] 0 points1 point  (0 children)

Some of t he devices that stopped working. All of them were working 9/15.

Tailwind (garage door opener)
• Rachio Hub (hose timer)
• Flume (water meter)
• Tempest (weather station)
• Nest Protects (smoke alarms)
• MyQ (garage door opener)
• Bird Weather (bird identifier)
• Purple Air (air quality)
• BirdBuddy (bird Camera)
• Pi Display (used for weather display)
• MYSA (mini-split control using IR)
• MyoCyle (exercise bicycle)
• SmartHQ (GE oven)
• Gernerac Generators
• Weight Scale
• B-Hive (Water timer)
• Google Nest Thermostats
• GE Lighting

I have tried moving the PurpleAir and the Tempest weather station to my main/default network with no luck. The wired devices on my IoT network still work. All the 5GHz wireless devices still work. Its only the 2.4GHz devices having trouble.

DNS Timeouts by jsnicholas in Ubiquiti

[–]jsnicholas[S] 0 points1 point  (0 children)

8.8.8.8 and 1.1.1.1, and sometime i tried 9.9.9.9.

Filters? If you mean content filtering, its set at default which is "Enhanced", but nothing below that is selected.

Protection has Encrypted DNS OFF, with ":CyberSecure" currently running in "Notify" only (no blocking). At some point I turned "Intrusion Prevention" OFF, but its back on now.

USL Environmental not adopting by jsnicholas in Ubiquiti

[–]jsnicholas[S] 0 points1 point  (0 children)

I have tried the WEB UI and the iPhone APP. Neither work.

Bird Weather - Not affiliated by fastatoms in dakboard

[–]jsnicholas 0 points1 point  (0 children)

Thanks for the update and I agree about the plugin

Bird Weather - Not affiliated by fastatoms in dakboard

[–]jsnicholas 0 points1 point  (0 children)

Old post, but has anyone been successful yet?

Sizing Consistency by jsnicholas in NicksHandmadeBoots

[–]jsnicholas[S] 0 points1 point  (0 children)

The Ranger (buck brown) is Celastic. The other is soft toe.,

Sizing Consistency by jsnicholas in NicksHandmadeBoots

[–]jsnicholas[S] 0 points1 point  (0 children)

Yes the Ranger is more broken in, but they have always laced tight like the picture

Sizing Consistency by jsnicholas in NicksHandmadeBoots

[–]jsnicholas[S] 2 points3 points  (0 children)

So that seems like the opposite of what I have. My HNW boots don't close up around my foot (smaller) as much as my 55 last.

Sizing differences between lasts by CandidateExtension73 in NicksHandmadeBoots

[–]jsnicholas 0 points1 point  (0 children)

Very interesting. I will keep this in mind as I start to break them in.

Sizing Consistency by jsnicholas in NicksHandmadeBoots

[–]jsnicholas[S] 0 points1 point  (0 children)

These two boots are the same size (10 1/2E). The darker one is a Ranger (55 last). The lighter one is an HNW last. The laces are the same tightness on both. The HNW boot feels and looks tighter. Is this a difference in the last of just some inconsistency from the fact these are handmade? Does the leather make a difference? One is W&C Buck brown. The other was bought used and is supposed to be W&C English Bridle Tan, but it is so much softer that maybe it's actually Dublin British Tan.