Veritas InfoScale™ 7.4.3 Solutions Guide - Linux
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- Section III. Stack-level migration to IPv6 or dual stack
- Section IV. Improving database performance
- Overview of database accelerators
- Improving database performance with Veritas Concurrent I/O
- Improving database performance with atomic write I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Backing up and recovering
- Preserving multiple point-in-time copies
- Online database backups
- Backing up on an off-host cluster file system
- Database recovery using Storage Checkpoints
- Backing up and recovering in a NetBackup environment
- Off-host processing
- Creating and refreshing test environments
- Creating point-in-time copies of files
- Section VI. Maximizing storage utilization
- Optimizing storage tiering with SmartTier
- Optimizing storage with Flexible Storage Sharing
- Optimizing storage tiering with SmartTier
- Section VII. Migrating data
- Understanding data migration
- Offline migration from LVM to VxVM
- Offline conversion of native file system to VxFS
- Online migration of a native file system to the VxFS file system
- VxFS features not available during online migration
- Migrating storage arrays
- Migrating data between platforms
- Overview of the Cross-Platform Data Sharing (CDS) feature
- CDS disk format and disk groups
- Setting up your system to use Cross-platform Data Sharing (CDS)
- Maintaining your system
- Disk tasks
- Disk group tasks
- Displaying information
- File system considerations
- Specifying the migration target
- Using the fscdsadm command
- Maintaining the list of target operating systems
- Migrating a file system on an ongoing basis
- Converting the byte order of a file system
- Migrating from Oracle ASM to Veritas File System
- Section VIII. Just in time availability solution for vSphere
- Section IX. Veritas InfoScale 4K sector device support solution
- Section X. Reference
About Just In Time Availability
The Just In Time Availability solution provides increased availability to the applications on a single node InfoScale Availability cluster in VMware virtual environments.
Using the Just In Time Availability solution, you can create plans for:
Planned Maintenance
Unplanned Recovery
In the event of planned maintenance, the Just In Time Availability solution enables you to clone a virtual machine, bring it online, and failover the applications running on that virtual machine to the clone on the same ESX host. After the maintenance procedure is complete, you can failback the applications to original virtual machine. Besides failover and failback operations, you can delete a virtual machine clone, view the properties of the virtual machine and its clone, and so on.
When an application encounters an unexpected or unplanned failure on the original virtual machine on primary ESX, the Just In Time Availability solution enables you to recover the application and bring it online using the unplanned recovery feature.
With
, the Just In Time Availability solution enables you to set up recovery policies as per your requirement to mitigate the unplanned failure that is encountered by an application. Just In Time Availability solution provides the following recovery policies for your selection. You may select one or all the recovery policies as per your need.Unplanned Recovery Policies | Description |
---|---|
Restart Application | Just In Time Availability (JIT) solution attempts to restart the service group (SG), and bring the application online on the original virtual machine on primary ESX. Maximum three retry attempts are permitted under this policy. Note: If all the three attempts fail, application continues to remain in faulted state or continues with the next policy as selected while creating a plan. |
Restart virtual machine (VM) | Just In Time Availability (JIT) solution performs the subsequent tasks such as bring the service group offline and shuts down the virtual machine; powers on the virtual machine; bring the service group online on the original virtual machine on primary ESX. You are provided with Last attempt will be VM reset option to reset the virtual machine. By default, this checkbox is selected and the default retry attempt value is one. If you retain the default settings, then VM reset operation is performed on the virtual machine at the first attempt itself. Maximum three retry attempts are permitted for this operation. If you deselect the checkbox, then the virtual machine reset (VM Reset) operation is not performed. |
Restart VM on target ESX | Using this policy, you can recover the faulted application on the virtual machine. In this policy, the original virtual machine is unregistered from the primary ESX; registered on the target ESX; and the faulted application is brought online on the virtual machine. Note: While configuring Restart VM on target ESXpolicy, ensure that the ESX version of both the source and target is compatible with each other. The virtual machines on target ESX are registered with the same vmx file as on the source ESX. |
Restore VM on target ESX | Using this policy, you can recover the faulted application on the virtual machine using a boot disk backup copy of the original virtual machine. In this policy, the original virtual machine is unregistered from the ESX and the boot disk backup copy of the original virtual machine is registered on target ESX. The faulted application is then brought online on the virtual machine. Note: While configuring Restore VM on target ESX policy, ensure that the ESX version of both the source and target is compatible with each other. The virtual machines on target ESX are registered with the same vmx file as on the source ESX. |
Unplanned Failback | The Unplanned Failback operation lets you failback the application from the boot disk back up copy of virtual machine on the target ESX to the original virtual machine on primary ESX. If you have selected either Restart VM on target ESX or Restore VM on target ESX or both the recovery policies, you can perform the Unplanned Failback operation. On the Plans tab, in the plans table list, right-click the virtual machine and click . Note: Unplanned Failback operation operation is disabled and not available for the plans and the virtual machines which have Restart Application and Restart VM policies as the only selected options. |
Based on the selected recovery policy for a plan, Just In Time Availability (JIT) solution performs the necessary operations in the sequential order.
For example, if you have selected Restart Application and Restart VM as the recovery policy, then in the event of unplanned application failure, first it performs tasks for Restart Application policy and if that fails, it moves to the next policy.
You may select one or all the recovery policies based on your requirement.
Table: Tasks performed for each Unplanned Recovery policy lists the sequence of tasks that are performed for each Unplanned Recovery policy.
Table: Tasks performed for each Unplanned Recovery policy
Unplanned Recovery Policy | Tasks Performed |
---|---|
Restart Application |
|
Restart virtual machine (VM) |
|
Restart VM on target ESX |
|
Restore VM on target ESX |
|
Unplanned Failback |
|
While creating a plan for unplanned recovery, with
, you can set up a schedule for taking a back up of boot disk of all the virtual machines that are a part of the plan.To use the Just In Time Availability solution, go to vSphere Web Client > Home view > Veritas AppProtect.
See Setting up a plan.