![]() Azure Site Recovery provides disaster recovery.When Infinite i migrates the database, it creates a database schema that maps physical files to tables and logical files to views. These options support the same features as the internal database. The database options are: SQL Server, Azure SQL, Oracle, and MySQL. ![]() Instead of the internal database that step 5 describes, you can migrate the DB2/400 database to a standard SQL database.The file share also holds load modules and log files. Mounting a file share on the Azure VM gives programs direct access to the files. Azure Files provides file shares to implement Infinite i files.Infinite i provides internal database connectors (ODBC and JDBC) for connecting to physical and logical files in the internal database. When an application runs on Azure, it accesses data as it did in the AS/400 environment, with no code changes required. An Infinite i internal database emulates the behavior of a DB2/400 database, including features such as physical files, logical files, multi-member files, joins, triggers, referential integrity, commitment control, and journaling.The compilers translate System i source code to 64-bit object code that runs on Azure x86 VMs.Infinite i supports an active-passive configuration (one active VM, one standby VM). ![]() The architecture uses two or more VMs for high availability, and Azure Load Balancer controls inbound and outbound network traffic. Each server runs in its own Microsoft Azure Virtual Machines VM.
0 Comments
Leave a Reply. |