Operating Requirements
In a VM environment that supports live migration, an authorized Pervasive PSQL Vx Server instance—along with your application—can move from one host to another host with no impact to your end users. (Contrast this with a traditional client/server environment in which the physical server normally remains consistent. Clients may connect and disconnect, but they communicate with a dedicated server. )
Obviously, the operating requirements for Pervasive PSQL Vx Server must differ from those for Pervasive PSQL Server and Pervasive PSQL Workgroup because of fundamental differences between VM and traditional environments.
The following table explains the operating requirements for Pervasive PSQL Vx Server.
Table 1
Operating Requirements for Pervasive PSQL Vx Server
Machine Requirement
Discussion
Internet connectivity at all times
Pervasive PSQL Vx Server periodically verifies that the key for the database engine is still valid. The validation requires Internet connectivity.
You have 30 days to restore connectivity and re-validate the product if the network loses Internet connection.
Consistent Hostname and Network Interface Card (NIC) MAC addresses
An authorized instance of Pervasive PSQL Vx can be moved to a different physical machine, or converted into a VM, or migrated to a different VM host.1 However the VM hostname and VM NIC MAC addresses must remain the same. If one of these must change, deauthorize the key for Pervasive PSQL Vx Server before performing the move, conversion or migration. See also FAQs About Hypervisor Products and Pervasive PSQL Vx Server Licensing.
1 Each instance of Pervasive PSQL Vx Server, including those that are cloned or copied for VMs, requires its own permanent key even if the hostname and MAC addresses are the same. See also Licensing.