Patch Release v2.3.4

Changes:

1. User authentication fix to support AD, Tenant and combinations.
2. Option to provide network name, folder name and interface name while restoring VM.
3. Updated documentation.

Job creation: Indexing Policy will be enabled by default

Changes:

1. While job creation, indexing policy will be enabled by default.
2. Users can provide custom allow deny prefixes. If not provided, default allow/deny prefixes will be added.
3. During job update, indexing policy and prefixes will be overrided if values are changed.

v2.3.2

Enhancement:

• Support Cohesity-Agent installation/uninstallation for OracleLinux operating system.
• Agent Installation support using both script and native installer.

Changes:

• Improved yaml lint score of all the playbooks.

v2.3.1

Enhancements:

• Added Documentation for Oracle workflow.

Fixes:

• Oracle database restore to clone app view without viewname.

v2.3.0

Enhancements:

• Agent installation/Uninstallation support for AIX and SLES.
• Vmware file recovery.
• Backup list of databases from a Oracle server.
• While job creation, if timezone is not provided, local system timezone will be used.
• Updated playbooks to fetch credentials from inventory file.
• Option to remove sources in Physical Protection Job.
• Vmware VM restore based on recovery type kInstantRecovey or kCopyRecovery.
• Updated playbooks to fetch cluster credentials from inventory file.

Bug Fixes:

• While fetching VMware sources, issue when endpoint is registered using ip.
• Run job right after job creation fails, but job run is successfully triggered.

Release with timezone and start_time fix

Added 'user-agent' field to all API headers.

Issue:
While job creation, start_time and time_zone are not updated correctly if mentioned in the playbook.

Fix:

1. Supports option for start_time(supports military time). Accepted formats include HHMM and HH:MM.
2. Supports following lists of timezones available in pytz.all_timezones module.

Patch release for exclude filepath issue(PhysicalFiles)

Issue:

1. When a Cohesity protection job is defined via Ansible WITHOUT "excludeFilePaths" set the protection job is successfully created. Immediate & subsequent runs of the exact same playbook fail with the error until "excludeFilePaths" is defined.
2. When a Cohesity protection job is defined via Ansible WITH "excludeFilePaths" set the protection job is successfully created. If you undefine "excludeFilePaths" later the playbook fails with an error unless at least ONE "excludeFilePaths" is defined per included path.

Fixes:
Exclude filepaths is made optional while creating/updating a job.

Tests:
Tested in 6.5.1 cluster

Trigger protection job run against Specific source

Issue:
Starting a protection run, triggers backup with all the sources available in the job even if only few sources are mentioned.

Fix:
If sources are mentioned, only specified sources are added to the job run. If source is not mentioned, all the sources available in the job are added to the run.

v2.1.1

Issue:
During vmware job update, include vms overwrites the existing vms protected by the job.

Fix:
Flag is added(replace_existing), if flag is set to true, existing job vms will be replaced with new include vms.
If flag is set to false, new include vms will be added to existing vm list available in the job.

v2.1.0

Enhancements:

• New modules cohesity_oracle_source, cohesity_oracle_job, cohesity_oracle_restore are added.
• Oracle source can be registered and unregistered using cohesity_oracle_source.
• New oracle source protection job is created using cohesity_oracle_job.
• Oracle databases can be restored using cohesity_oracle_restore.
• Added sample playbooks.

Bug fixes:

• During protection job updation, source filepaths are updated along with source ids.