AF Failover Processing

Discussion created by markshannon on Jul 8, 2014
Latest reply on Jul 9, 2014 by bperry

We have PI AF set to function as a primary and a failover(secondary) component ie a collective. Our primary is located on a virtual server and our failover is located on a second and separate virtual server. Recently, we encountered an event which triggered our failover component to become the primary. However, we found that while our seconday SQL Server DB (AF) had been getting backed up, the AF Databases and supporting components have not been migrated from our primary to secondary version.. our secondary version showed as the most current data from 3 months ago.


I know that PI AF has a component option to refresh under the PI Collective tab. Do any of you know of a way to automate or emulate in an automated fashion the refresh feature of PI AF Collective?