OS Support Limitations

This table below defines the limitations for each supported Operating System running in an appliance on AppLogic.

Prior to AppLogic 2.4.7, Windows appliances may have a maximum of 7 terminals. In AppLogic 2.4.7, Windows appliances may have a maximum of 8 terminals.

Inside of an appliance, any file system may be used on an AppLogic volume that is supported by the appliance's operating system. The file systems listed above are the ones that are supported/recognized by AppLogic. Any volume that uses a file system that is not recognized/supported by AppLogic is reported as raw.

iso9660 is a cd-rom/iso file system; iso9660 cannot be created using the AppLogic filers

ntfs and ntfs03 refer to the same file system.

Please review the AppLogic release notes for a list of all known issues, limitations and bugs in AppLogic and the supported OSes.

Maximum number of appliances per server

• AppLogic 2.4.5 : 40 appliances per server. For OpenSolaris, 16 appliances per server without hotfix e2648 installed.
• AppLogic 2.4.7+ : 50 appliances per server

Maximum number of volumes per server

• AppLogic 2.4.5 : 256 volumes per server.
• AppLogic 2.4.7+: 1024 volumes per server.

Only 256 volumes may be mounted or in-use on a single server at any one time.

Known Limitations and other notes

OpenSolaris

• All OpenSolaris appliances distributed with AppLogic are based on build 2008.05.
• OpenSolaris installations are not supported by iso2class; this is due to a bug in OpenSolaris that prevents the GUI from working correctly. Please use the OpenSolaris appliances that are distributed with AppLogic.

Solaris 10

• AppLogic does not distribute any Solaris 10 appliances or applications due to licensing restrictions. However, AppLogic does support Solaris 10 based appliances. Solaris 10 appliances may be created using the new iso2class utility. See the Solaris 10 data sheets in the catalog reference/application reference for more information on how to create your own Solaris 10 based appliances/applications (filer, VDS, etc).
• iso2class may be used to install a Solaris 10 appliance using the graphical console for the installation process. However, after the installation is complete and the appliance is re-started, the graphical console may still be used however it must be used in text mode (no access to the Solaris 10 desktop - strictly text-based access). This is due to a problem in the Solaris 10 GUI (not an AppLogic bug).

Windows 2003 Server

• AppLogic does not distribute any Windows 2003 Server appliances or applications due to licensing restrictions. However, AppLogic does support Windows 2003 Server-based appliances. Windows appliances may be created using the new iso2class utility. See the Windows Installation Reference for more information on how to obtain/create Windows based appliances/applications (filer, server, VDS, etc).
• Please see the AppLogic 2.4 release notes for a list of known issues when using Windows appliances on your AppLogic grid.

ntfs support in AppLogic

• AppLogic only supports Microsoft Windows NTFS v5.2 that is used in Windows Server 2003.
• The AppLogic Windows filer does have some specific limitations for NTFS volumes; please see the Windows filer datasheet for more information.

zfs support in AppLogic

• The AppLogic Solaris filer that is used for Solaris volume operations does support zfs. However, currently this is limited to single device zfs pools. In order to take full advantage of all of the zfs capabilities under AppLogic, users may assemble their own zfs pools inside of their own appliances. If a zfs pool is going to be used for mirroring, the AppLogic volumes that are used in the pool should be created with the AppLogic mirroring disabled (using the mirrored=0 option when creating the volumes). Please see the Solaris filer data sheet for more information on all of the zfs limitations.
• Solaris 10 uses an older version of zfs that is incompatible with the version of zfs used by OpenSolaris 2008.05 and does not work with the AppLogic filer. However, zfs may still be used if the user manually assembles their own zfs pools in their Solaris 10 appliance.
• AppLogic 2.3+ does support booting Solaris appliances from a zfs boot volume. However, this has not been verified by 3tera. If you are having problems booting Solaris appliances from zfs boot volumes, please contact Technical Support.
• The Solaris filer does not support root zpools (zfs boot volumes). There is a bug in OpenSolaris 2008.05 which renders a root zpool un-bootable once it has been imported into another Solaris OS.
• The AppLogic Solaris filer does have some specific limitations for zfs volumes; please see the Solaris filer datasheet for more information.

-- BeckyH - 30 Apr 2008