One way to simplify this is to use substitution parameter for the PI Server referenced by attributes with PI Point Data Reference. The substitution parameter %Server% should be replaced with the default PI Server of the AF Server. This should avoid the need to manually update the server references. If you are using templates on the production server, changing this should be relatively easy. This would be quite helpful especially when you are mainly using 1 PI Server.
A thing to take note is that if is possible that the attribute lock in the config settings, for example if you are using templates and "Create or Update PI Points" is used on the attribute. After that operation, the setting is always pointing to the same server, instead of dynamically replacing the substitution parameter. You can use the "Reset to Template" option to revert it. It is possible to do this in bulk using PI System Explorer or using the AF Builder add-in in Excel.
Taking a backup and restore the PIFD database in the test environment should work as well. You probably want to install AF Server in the test environment and test the connection before you restore the PIFD database from production. This is to ensure that the things that the required user groups are created during the installation. Substitution parameters should still be effective even if you use this method.
One pitfall that I would look out for is if you have the MDB-AF sync setup. When you migrate to a new server environment, AF Link subsystem will probably fail, because the underlying ID of the new environment is different from the production environment. In this case , it will be required to set it up again.
Thanks Han. I also posted to tech support and they suggested an Alias to the Test PI server. If I do a backup restore of AF and have an Alias for the prod PI server name pointing to test it appears too work without requiring any modification
Yup, That would be a good suggestion as well
I am doing the similar excerise. Currenly In our test AF/PI server the asset data and tag data are old . I plan to move the production server PI data and AF data from Prod servers to test server. Can you please suggest any caveats/steps involved.
I also posted to tech support and they suggested an Alias to the Test PI server.
To open the aliases dialog in PISDKUtility.exe, select "Connections" in the pane on the left hand side and select "Aliases..." from the "Connections" menu.