Version 16.0

December 1, 2022

Release Overview

The new features:

Epic/Module

Story/Task

Description

Native SQL Backup

https://accelario.atlassian.net/browse/LOKI-1684

"Create" Test Data Environment with a "Native SQL Server Backup" GI

Native SQL Backup

https://accelario.atlassian.net/browse/LOKI-1715

"Activate" a newly created "Native SQL Backup" GI

Native SQL Backup

https://accelario.atlassian.net/browse/LOKI-1725

modify DB parameters to Add/Modify DB Home

VDB Management

https://accelario.atlassian.net/browse/LOKI-1733

Change Snapshot section of VDB Management screen to enable managing hundreds of snapshots

MS-SQL

https://accelario.atlassian.net/browse/LOKI-1609

Installing source agent (demo)

MS-SQL

https://accelario.atlassian.net/browse/LOKI-1619

Add Windows Source Host

MS-SQL

https://accelario.atlassian.net/browse/LOKI-1611

Creating Test Data Environment with a MS-SQL LIVE GI (demo)

MS-SQL

https://accelario.atlassian.net/browse/LOKI-1625

Add Windows Target Host

MS-SQL

https://accelario.atlassian.net/browse/LOKI-1613

Adding MS-SQL Home on a Target Host

MS-SQL

https://accelario.atlassian.net/browse/LOKI-1614

Creating a VDB on a MS-SQL LIVE GI snapshot (demo)

MS-SQL

https://accelario.atlassian.net/browse/LOKI-1626

Start/Stop a MS-SQL VDB

GI Management

https://accelario.atlassian.net/browse/LOKI-1523

Create REST API in swagger to check creation status of GI volume

VDB Management

https://accelario.atlassian.net/browse/LOKI-1502

Disable all log_archive_dest_* except for one we use during recovery of VDB.

VDB Management

https://accelario.atlassian.net/browse/LOKI-1401

Show on what snapshot a VDB was created (extention)

GI Management

https://accelario.atlassian.net/browse/LOKI-1308

Display "CREATE STANDBY RMAN GI" in VDB Management screen for standby rman gi

VDB Management

https://accelario.atlassian.net/browse/LOKI-1545

Allow to change advanced custom parameter name

Agents

https://accelario.atlassian.net/browse/LOKI-1668

Improve dynamical error codes exclusion for GI/DST Agents

Server

https://accelario.atlassian.net/browse/LOKI-941

Provide some advanced db parameters preinstalled

Server

https://accelario.atlassian.net/browse/LOKI-1663

VDB Management. Remove the number 1 when the VDB is raised by one RAC instances

Agents

https://accelario.atlassian.net/browse/LOKI-992

Add log files to agents

TDE Management

https://accelario.atlassian.net/browse/LOKI-1726

Remove "Test Connection" from Create Test Data Environment for LIVE GI

Important fixed bugs:

Epic/Module

Bug

Description

VDB Management

https://accelario.atlassian.net/browse/LOKI-1105

Different time in snapshot name and "created" field (bug)

GI Management

https://accelario.atlassian.net/browse/LOKI-1622

After deletion of Golden Image, the acc server does not delete the directory itself

Server

https://accelario.atlassian.net/browse/LOKI-1631

Error message and empty pop-up after click 'Last Logs' or 'Log History' button into 'Info pop-up for LIVE GI

The list of known issues found during the last release:

Issue key

Summary

LOKI-1823

VDB management. MSSQL. 'Stop VDB error: Invoke-Sqlcmd : Database 'qatest1' is in transition' if another VDB is under creation

LOKI-1817

Server | MSSQL database name validation. Invalid validation №2

LOKI-1816

Server | MSSQL database name validation. Invalid validation

LOKI-1812

VDB management. Error about fail MSSQL connection is shown with successfully connection

LOKI-1811

VDB management. Only part of database name shown in the info pop-up of VDB

LOKI-1810

VDB management. MSSQL. Incorrect message if try to create VDB with existed db name

LOKI-1809

API. VDB Management. The system allows you to activate the active GI

LOKI-1808

VDB management. Incorrect label for autosnapshot for Native SQL GI

LOKI-1804

API. VDB Management. Native Backup. Can create 2 Native Backup GI on one page

LOKI-1803

VDB management. previous instance name isn't shown after stop VDB in MSSQL

LOKI-1802

VDB management. Disabled Name and description fields in Start VDB pop-up for Oracle

LOKI-1800

VDB management. Connection info is missing for Native MSSQL GI

LOKI-1799

VDB management. The port field is present in the info pop-up for Live GI MSSSQL

LOKI-1792

Source Management. It is not possible to create TDE MSSQL with the same field value Database Name

LOKI-1789

VDB management. MSSQL. Uncleared error messages for failed autosync with incorrect settings

LOKI-1787

VDB management. Huge time to download snapshots page with 1000 snapshots

LOKI-1778

MSSQL VDB failed if another one is under creation on the same dst agent

LOKI-1772

Refresh GI completed successfully but a snapshot not created

LOKI-1764

VDB management. Initiall load process isn't shown on UI

LOKI-1761

No log is shown for Live GI MSSQL

LOKI-1757

When starting VDB MSSQL, an instance name is required but it is not used

LOKI-1738

Activate GI Postgres gives incorrect message when the database is not in recovery mode

LOKI-1682

Source management. Unmount of Oracle LIVE 12 doesn't happen after deleting TDE from UI

LOKI-1674

RAC-to-RAC VDB start fails due to PRCR-1086 : server pool ora.<SID> is already registered

Testing status:

  • The regression tests -  completed 

https://docs.google.com/spreadsheets/d/18JXYqfgl0T6KtpWdrR6W9JAlS5I9jA1Z/edit?pli=1#gid=1742277043

All critical bugs found during the regression testing have been fixed.

  • All supported versions have been tested and work as expected:

    • ORACLE

      • RMAN v11

      • RMAN v12

      • LIVE v12

      • RMAN v19 nonDG

      • RMAN v19 StandBy + same host

      • RMAN v19 RAC-to-single

      • RMAN v19 RAC-to-RAC

      • LIVE v19

    • PostgreSQL

      • LIVE v13 ubuntu 20

      • LIVE v13 RHEL/CentOS 7

      • LIVE v13 RHEL/CentOS 8

      • LIVE v14 ubuntu 20

      • LIVE v14 RHEL/CentOS 7

      • LIVE v14 RHEL/CentOS 8

    • MSSQL

      • LIVE v2016 Windows Server 2012R2

      • Native Backup v2016 Windows Server 2012R2