Download Sun Virtual Desktop Infrastructure

Sun Virtual Desktop Infrastructure 3.0
the SRS datastore, but this created several issues. In VDI 3, the read/write cycles/frequency are higher compared to VDI 2 and
thus an LDAP based datastore was no longer the best suitable choice.
What are the requirements for High Availability in a VirtualBox
backend?
What are the requirements for High Availability in a VirtualBox backend?
High Availability for a VirtualBox virtualization platform would require at least 2 VirtualBox hosts. In the event that one VirtualBox
server goes down, all existing desktop sessions would be terminated. Then the terminated sessions would be restarted on the
remaining VirtualBox server(s) as they are requested by users, as long as there is sufficient memory available.
High Availability for The VDI Core, Sun Ray, and MySQL requires a Primary node, and 2 Secondary nodes. See Supported
Configurations for detailed information about the hardware configurations that support this type of redundancy.
What happens when the Primary VDI Core host fails?
What happens when the Primary VDI Core host fails?
Assuming you have three VDI Core hosts and one of them is the primary, if the primary goes down the following happens:
The underlying database is still running on the remaining hosts.
All desktop sessions are still running on the remaining hosts.
New session requests will be handled by the remaining hosts.
All desktops are still running on the virtualization hosts.
So in essence, your VDI cluster is still healthy. The operation is just impacted in this way:
You can't add new VDI core hosts.
You can't change the configuration of the Sun Ray server failover group.
A failure of another VDI core host (data node) will result into a complete outage of the underlying database.
You should bring up the primary again as soon as possible in order to gain failover capabilities again.
What is the difference between Personal and Flexible desktop
assignments?
What is the difference between Personal and Flexible desktop assignments?
Personal Assignment: Desktops which have been personally assigned to users are owned by these users (similar to the
personal computers under their desks). Thus they will never be recycled and will never become available for other users.
(However, an administrator can explicitly remove the assignment and re-assign a desktop to a different user.)
Flexible Assignment: Desktops which have been flexibly assigned are temporarily owned by users. Once users log out of
their desktops or their desktops are no longer in use, they will be recycled and become available for other users. As part
of the recycle process the desktop assignment will be removed.
Personal assignments are created when you select a specific desktop in the VDI Admin GUI and assign it explicitly to a user.
If you assign a user (or a group of users) to a pool, the desktop assignments are created on demand the first time the user
requests a desktop (or connects to a desktop). The type of assignment (personal or flexible) depends on the pool settings. You
can configure this individually for each pool on the Pool - Settings subcategory (see the Desktop Assignment section).
In addition to the assignment type, you can also specify how each pool is filled with desktops. Here you have the choice to
manually import desktops, or to clone desktops automatically from a specified template (see the Cloning subcategory).
When you create a new pool we provide default settings for the assignment and cloning configurations. For convenience, the
pool wizard offer "Manual", "Dynamic", and "Growing" pool types which only differ in their default settings. You can change the
pool settings at any point. The pool type is not stored anywhere - it just defines the initial pool settings and is offered as a
196