Best Practices for Transferring PI Vision Database and Configuration to a New Environment

Best Practices for Transferring PI Vision Database and Configuration to a New Environment

If you're tasked with migrating your PI Vision system to a new environment, it's crucial to ensure that both your data integrity and user access are maintained throughout the transition. Whether you're consolidating environments or moving to a more robust server, this guide will walk you through the essential steps of transferring your PI Vision database and configurations.

Step 1: Backup the PI Vision Database

The first step in the migration process involves securing a backup of your current PI Vision SQL database. This is your safety net in case anything goes awry during the migration process. Keep in mind that SQL databases can have specific dependencies and settings that need careful attention during migration.

Step 2: Install the Same PI Vision Version on New Server

Consistency is key for a smooth transition. Therefore, before proceeding, ensure that the PI Vision version installed on your new environment matches the one from the source. Consult the PI Vision installation and administration user guide for a step-by-step installation process.

Step 3: Configure User Accounts for Database Access

You'll need to create a local user account for database access. Make sure this account has the necessary privileges to interact with both the PI Vision database and any associated data sources.

Step 4: Set Appropriate Security Permissions

Security is paramount, especially when dealing with data-rich environments like PI Vision. Ensure that the user accounts are granted appropriate access levels to the PI and AF servers in the workgroup environment. This might involve configuring Windows security settings if your PI system uses Windows authentication.

Step 5: Update Display Server References

Use the PI Vision display utility tool to change any references to the PI Data Archive or AF server names for existing displays. This tool is invaluable for ensuring your displays point to the correct servers after migration.

Step 6: Add Users to Local PI Vision Users Group

For your users to continue accessing PI Vision smoothly, ensure they are added to the local PI Vision users group on the new server. This allows them the necessary permissions needed to interact with PI Vision.

Step 7: Cross-Domain Access Considerations

In a workgroup environment, especially across non-trusted domains, leverage the Windows Credential Manager and ensure NTLM authentication is configured. This will help maintain connectivity and access integrity.

Final Thoughts

While these steps provide a roadmap for migrating PI Vision, always refer to the official OSIsoft documentation for comprehensive details tailored to your specific configuration and version. Migration can have unexpected challenges, and official guides can offer solutions that are up-to-date with the latest best practices and software updates.

By following these structured steps, you can help ensure a smooth transfer of your PI Vision environment to a new server, minimizing downtime and maintaining the integrity and availability of your data displays.