Jump to content

Replace Polisy with eISY after major crash of Polisy


Recommended Posts

Posted

I'm dead in the water with my Polisy and no one from UDI Support has reached out yet (opened ticket about 4 1/2 hours ago. In fairness it's the weekend and I'm 3 hours ahead - but I am dead in the water so am urgently looking for solution to restore my HA)

On possible solution I might have is to restore IoX and PG3x from backups onto an eISY I've been using for testing and, frankly, in case of a catastrophic failure, which I think this might be. (the /var/udx folder is missing so I suspect disk corruption)

My eISY has it's own separate Zwave dongle (USB) and, from what I'm reading, I think I would need to create a "migration" backup (different from a regular one) on the Polisy in order to restore IoX on the eISY because of the different zwave dongles

Is that right or am I misreading things? (I've posted the relevant user guide section below)

If so - and I need to do step 3 below - that's a problem because I can't get into IoX on my Polisy to do that. If not, I do have a regular backup from a day or two ago I could use.

Can someone confirm whether or not I would have to do a migration backup in order to be able to switch over to my eISY? Is an alternative to swap the guts of my USB dongle with the "on board" zwave dongle from the Polisy? Is that physically do-able?

Any help would be appreciated.

 

Quote

Preparing for Migration from Eisy / Polisy

You can migrate locally on the same Eisy / Polisy or to another Eisy / Polisy.

On the Eisy / Polisy your are migrating from

  1. Make sure Eisy / Polisy is up to date
    •   Go to Admin Console configuration page and select Upgrade Packages
  2. If you are not migrating your Z-Wave network
    •   Use (Admin Console | File | Backup ISY) to make a backup of your Eisy / Polisy
  3. If you are migrating your Z-Wave network
    •   Leave your current Z-Wave board / dongle connected
    • Go to configuration tab in Admin Console and select "Migrate to ZMatter Z-Wave"
    • Choose the option that allows you to create a "migration" backup (first option)
    • You will see a series of popup windows providing information and asking simple questions
    • Once you have your "migration" backup you are ready to migrate
    • A migration backup is different than a regular backup.
    • When a migration backup is restored it also migrates your Z-Wave network

 

 

Posted

UD support is usually not available on Saturday, but you should hear back from them within the next day. It's best to get your Polisy up and running in order to migrate.

What zwave dongle(s) are you using on the Polisy and EISY?

Zwave needs to be backed up separately and in addition to Insteon. 

 

 

  • Thanks 1
Posted
19 minutes ago, Techman said:

UD support is usually not available on Saturday, but you should hear back from them within the next day. It's best to get your Polisy up and running in order to migrate.

What zwave dongle(s) are you using on the Polisy and EISY?

Zwave needs to be backed up separately and in addition to Insteon. 

 

Both are Zmatter. Polisy has the one installed inside the box, while eISY has the external plug-in USB version. Yes, I do zwave backups in AC regularly before doing IoX backup.

Can I not just restore IoX then do "Restore Zwave" on eISY given both are Zmatter? It doesn't say that in the user guide but that would be nice to allow for a cold standby solution to hardware failure.

 

Posted

It's best to wait for a response from UD support as I'm not sure what would happen to your programs if you didn't migrate both Insteon and zwave at the same time. 

Posted
4 hours ago, johnnyt said:

Both are Zmatter. Polisy has the one installed inside the box, while eISY has the external plug-in USB version. Yes, I do zwave backups in AC regularly before doing IoX backup.

Can I not just restore IoX then do "Restore Zwave" on eISY given both are Zmatter? It doesn't say that in the user guide but that would be nice to allow for a cold standby solution to hardware failure.

This is exactly what I did the other day, worked flawlessly.  If you're using PG3, you'll need to back that up as well, but restoring from backup was butter smooth.

Posted (edited)

Thanks, @jec6613.

It worked! One doesn't need a migration backup, a regular one will do, which makes sense and would be worth mentioning in user guide if anyone who can make changes to that is listening. Simply making it clear that a migration is only when moving from non-Zmatter to Zmatter would help because, to me, I was migrating from my Polisy to my eisy so was following that path.

Here are the steps I followed that worked. Note that this is when one does NOT have access to "old" unit so can't do a backup but, of course, has a backup, including zwave, from hopefully not too long before disaster hit:

1. Power off old Polisy/eisy (or unplug/remove Zmatter) if it isn't already dead so the old zwave dongle isn't fighting with the new one.

2. On the new eisy (or Polisy) make sure to enable Insteon (if applicable) and Zwave support, do "Upgrade Packages", reboot and let it finish. Process is faster/cleaner on a 'blank' eisy than on a fully configured one but can still take a while. (at >283 zwave nodes, 180 Insteon nodes, and >1100 programs, a reboot for me takes almost 10 mins.)

3. I did a shutdown of new eisy here but not sure it's required. I used SSH but on eisy you can push button 6 times (on Polisy its 3 times) to shutdown.

4. Move PLM over, restore IoX, which results in a restart / need to re-login, restore Zwave, which did not need a restart, restore PG3, and reboot (PG3 said it needed a reboot) 

5. Deal with fact that NS/plug-in licenses are tied to hardware and won't be active on your restored unit (although they will be there)

  • I've asked UDI to transfer the licenses over to new eisy because I won't need them on my Polisy anymore. Once it's fixed, it will become my lab/test unit and a 'cold backup' for any future disaster recovery

6. If applicable deal with things that changed after your backup was taken. (nothing in my case that I can fix. I did lose all my web server files (couple months of data), because they don't get backed up as part of IoX backup. A reminder than I have to do separate manual backup of those more frequently. I also lost a couple of days of variable values that are long term counters (e.g. furnace filter use, etc.) 

Now just waiting for response from UDI Support about fixing my dead Polisy. Turns out it's missing /var/udx - a key folder - and the disk is 100% full (every mount point at 100% except /tmpfs). Not good - guessing fixing it will take a while and maybe that's why they haven't responding yet.

At any rate I'm really glad my Disaster Recovery plan worked out. I've had duplicate hardware for a while but hadn't tested it yet. Too worried it would be fiddly but it was butter smooth as @jec6613 put it.

Edited by johnnyt
  • Like 2
Posted (edited)
On 1/21/2024 at 9:19 AM, johnnyt said:

Now just waiting for response from UDI Support about fixing my dead Polisy. Turns out it's missing /var/udx - a key folder - and the disk is 100% full (every mount point at 100% except /tmpfs). Not good - guessing fixing it will take a while and maybe that's why they haven't responding yet

I had the same failure on Friday. 100% full SSD. Michael checked several things, and we decided corupted SSD/file system is the likely cause, so restoring SDD from an image was the best course of action.

Here the process, though I'd wait until support contacts you, just incase they want to see if they can find the source of the missing disk space:
https://forum.universal-devices.com/topic/42174-polisy-ssd-image-restore-process-for-a-corrupt-ssd/

My eisy arrives tomorrow, so I'm glad to hear the restore from polisy backup to eisy  should be smooth and painless...

 

Edited by stevesreed
Guest
This topic is now closed to further replies.

×
×
  • Create New...