By protecting a copy of your VIs and, if possible, the configuration of your development or production machine before upgrading to LabVIEW 2013, you ensure that you can restore your VIs to their previous functionality and restart the upgrade process if necessary.
a. Back Up Your VIs
If you back up your VIs before you upgrade LabVIEW, you can quickly revert to the back-up copy. Without the back-up copy, you can no longer open upgraded VIs in the previous version of LabVIEW without saving each VI for the previous version.
You can back up a set of VIs using either of the following methods:
- Submit VIs to source code control—This action allows you to revert to this version of the files if you cannot address behavior changes caused by upgrading the VIs.
- Create a copy of the VIs—Create a copy of the VIs according to how they are organized:
- Saved as a project—Open the project and select File»Save As to duplicate the .lvproj file and all project contents. Ensure that you also maintain a copy of the files on which the project depends by selecting Include all dependencies.
- Saved as an LLB or as VIs in a directory—From the file explorer of your operating system, create a copy of the LLB or directory and store it at a different location from the original. To prevent possible naming conflicts, avoid storing the copy on the same hard drive.
b. Back Up Your Machine Configuration
Installing a new version of LabVIEW updates shared files in ways that sometimes affect the behavior of VIs even in previous versions. However, after you update those shared files, it is very difficult to restore the previous versions of the files. Therefore, consider one of the following methods for backing up the configuration of NI software on your development machine, especially if you are upgrading from an unsupported version of LabVIEW or if down time for your applications would be costly:
- Create a back-up image of the machine configuration—Use disk imaging software to preserve the disk state of the machine before you upgrade, including installed software, user settings, and files. To return the machine to its original configuration after you upgrade, deploy the back-up disk image.
- Test the upgrade process on a test machine—Although upgrading on a test machine requires more time than creating a back-up image, National Instruments strongly recommends this approach if you need to prevent or minimize down time for machines that control or monitor production. After resolving any issues that result from upgrading on the test machine, you can either replace the production machine with the test machine or replicate the upgrade process on the production machine.
||Tip To minimize the possibility that upgraded VIs on the test machine behave differently than on the development machine, use a test machine that matches the features of the development machine as closely as possible, including CPU, RAM, operating system, and versions of software.