How to prepare a backup ISY 994i ?

[telljcl]

I've picked up another 994izw pro for backup purposes (also another Insteon PLM to go with it).

I'd like to set it up as a backup to my primary ISY.

How should this be done, and how do the "Modules" or ISY Portal work in this regard (do I need to re-purchase these again for the backup unit?)

Unsure how this all would work.

Thanks for any direction.

 

[Hurting2Ride]

I'm curious about the answers to this as well.  I know there's at least a couple of people active on this forum that have multiple systems, although I don't know how they're being used (production, development, disaster recovery.)  Hopefully they can provide some insight.  Questions I have

1) do all modules need to be repurchased?   
         a. Does this depend on if the system is to be used only in case of 1st system hardware failure vs used for development or some other live use?
         b. if not,  in the event of 1st system hardware failure, how quickly can modules be moved from the 1st system to the 2nd ?

2) I'm assuming that other than keeping the 2nd system at the same release level as the 1st, there's not much "prep" that can be done to have the system take over from the 1st.   I'm assuming this because it seems like the idea of a 2nd PLM on the network with similar link tables would be asking for trouble.  But I'd happily be wrong.

3) is there any way to create an automated backup process either via the ISY UI itself or kicked off via command? or an acceptable "hack" that scripts the process?

4) all the other things I'm not thinking of...

 

 

 

[lilyoyo1]

If this is going to be a true backup (not used until the old goes bad) then udi can switch your modules over to the new one when the time comes that you need it. If your using it for testing etc. Then you will need to purchase the modules for it 

[paulbates]

@lilyoyo is correct. Neither the ISY or Insteon are architected / designed to be "active active" or "active passive"

You'll also want your ISY Portal content/configuration moved, which are UUID specific as well. I'm not sure if that can be done via a support ticket, but I'd ask

if you’re running v5 and nodeservers, you also have to think through IP addresses of the ISY and the local nodeserver server systems. If you have externally systems that contact the ISY like mobile apps, this needs to be thought through as well.

Treat the recovery of the PLM as separate. If my ISY were to die for some reason, I would move the current PLM over the the new ISY and follow the procedure above. I keep an additional PLM around just in case. Historically that has been the weak link, but with SmartLabs changes to PLM hardware in the past few years, I don't think anyone knows how much of a problem it is any longer. But as a key component and <$50 on sale, I'll always have a spare.

Paul

 

[Hurting2Ride]

Thanks.