OS Support Limitations

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

OS	Mode	Virtualization Mode	PV Drivers	Max Volumes	Max Terminals	Supported CA 3Tera AppLogic Filer File Systems	Max Volume Size
Linux	32/64-bit	Xen-Paravirtualized and VMWare-ESX	none	xen_pv: 12, xen_hvm/VMware: 4	Xen: 15, VMware: 10	ext2, ext3, ext3-snapshot, fat16, fat32, reiserfs, swap, iso9660	2TB-1MB 32-bit Linux limitation
OpenSolaris (build 2008.11)	32/64-bit	Xen-Paravirtualized	none	xen_pv: 12, xen_hvm/VMware: 4	10	ufssol, zfs, iso9660	ufssol: 1048575MB (1TB-1MB) zfs: limited only by available storage space on grid
Windows 2003 Server Standard/Enterprise/DataCenter/Web Editions	32/64-bit	Xen-Hardware-Emulation	Turbogate	4	8	ntfs, ntfs03, iso9660	2TB-1MB
Windows 2008 Server Standard/Enterprise/DataCenter/Web Editions	32/64-bit	Xen-Hardware-Emulation and VMWare-ESX	Turbogate	4	Xen: 8, VMware: 10	ntfs08, iso9660	2TB-1MB

Notes:

Inside of an appliance, any file system may be used on a CA 3Tera AppLogic volume that is supported by the appliance's operating system. The file systems listed above are the ones that are supported/recognized by CA 3Tera AppLogic. Any volume that uses a file system that is not recognized/supported by CA 3Tera AppLogic is reported as raw.
iso9660 is a cd-rom/iso file system; iso9660 cannot be created using the CA 3Tera AppLogic filers
ntfs and ntfs03 refer to the same file system.
Review the CA 3Tera AppLogic release notes for a list of all known issues, limitations and bugs in CA 3Tera AppLogic and the supported operating systems.
Solaris 10 does not work on CA 3Tera AppLogic 3.1 grids (for either Xen or ESX). This will be resolved in a future release.
OpenSolaris does not work on ESX-based CA 3Tera AppLogic 3.0 grids. This will be resolved in a future release.

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

OpenSolaris

All OpenSolaris appliances distributed with CA 3Tera AppLogic are based on build 2008.11.
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 CA 3Tera AppLogic.
OpenSolaris does not work on ESX-based CA 3Tera AppLogic 3.0 grids. This will be resolved in a future release.

Windows Server 2003 and Windows Server 2008

CA 3Tera AppLogic does not distribute any Windows Server appliances or applications due to licensing restrictions. However, CA 3Tera AppLogic does support Windows Server 2003 and Windows Server 2008 based appliances. Windows appliances may be created using the iso2class utility. See the Windows Installation Reference for details on how to create these appliances on your CA 3Tera AppLogic grid (under the "OS Installation" -> "Distributed Installations" section in the Appliance Developer's Guide).
See the CA 3Tera AppLogic release notes for a list of known issues when using Windows appliances on your CA 3Tera AppLogic grid.

NTFS support in CA 3Tera AppLogic

CA 3Tera AppLogic only supports Microsoft Windows NTFS v5.2 that is used in Windows Server 2003 and NTFS v6.0 that is used with Windows Server 2008.
CA 3Tera AppLogic ships with the Windows 2008 filer, the Windows 2003 filer is now obsolete. The Windows 2008 filer can handle volumes for both Windows 2003 and 2008 Server.
The CA 3Tera AppLogic Windows filer does have some specific limitations for NTFS volumes; see the Windows 2008 filer datasheet for more information.

ZFS support in CA 3Tera AppLogic

The CA 3Tera AppLogic Solaris filer that is used for Solaris volume operations does support zfs. However, currently this is limited to single device zfs pools. To take full advantage of all of the zfs capabilities under CA 3Tera 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 CA 3Tera AppLogic volumes that are used in the pool should be created with the CA 3Tera AppLogic mirroring disabled (using the mirrored=0 option when creating the volumes). See the Solaris filer data sheet for more information about all of the zfs limitations.
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. OpenSolaris 2008.11 does not support import of bootable zpools at all.
The CA 3Tera AppLogic Solaris filer does have some specific limitations for zfs volumes; see the Solaris filer datasheet for more information.