Version 17.0

February 1, 2023

Release Overview

The new features:

Epic/Module

Story/Task

Description

 

iSCSI for MS-SQL

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

Install a source agent in the Windows source host that will be used to iSCSI mount

 

iSCSI for MS-SQL

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

Install a target agent in the target Windows host that will be used to iSCSI mount

 

iSCSI for MS-SQL

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

Create/modify a MS-SQL Test Data Environment using iSCSI

 

iSCSI for MS-SQL

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

Create a VDB on an MS-SQL GI or VDB snapshot using iSCSI protocol

 

iSCSI for MS-SQL

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

Start MSSQL VDB Database Name field is optional

 

GI Management

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

Unmount all relevant mount points before GI creation (bug)

 

Duplicates

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

Allow use duplicates when only primary pool is defined and enable to choose the storage pool when creating duplicate

 

VDB Management

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

Warn the user when he tries to create snapshot on a failed VDB

 

Dataset

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

Datasets screen - number of Y-axis are not displayed correctly

 

Server

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

Always make available an option of "force stop VPD"

Michael

 

Important fixed bugs:

Epic/Module

Bug

Description

iSCSI for MS-SQL

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

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

iSCSI for MS-SQL

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

Rollback doesn't work for iSCSI MSSQL (Live + Native)

 

The list of known issues found during the last release:

Issue key

Summary

LOKI-1906

Pool management. Possible to create/expand pool by adding disk with incorrect path

LOKI-1905

VDB management. Incorrect message for LiveGI creation if main pool is absent

LOKI-1903

API. VDB Management. It is possible to delete the volume with snapshot(without VDB)

LOKI-1902

API. VDB Management. It is possible to edit the volume during creation

LOKI-1901

VDB Management. RMAN GI. After the volume is created, the snapshot is automatically deleted(floating bug)

LOKI-1900

Source Management. PG. Change the text of the error message

LOKI-1899

VDB Management/Source Management. The dbSid value is present in code for PG on MSSQL

LOKI-1878

Storage Pool Management. "Create secondary storage pool (for duplicates)" popup error

LOKI-1865

Long-term operations depend on an end-user token that can expire before the operation ends

LOKI-1850

VDB management. Huge time to download VDB tree with 10000 snapshots

LOKI-1849

Password for VDB updates system user password as well

LOKI-1848

VDB Management. RMAN GI is not deleted after force stop during creation

LOKI-1823

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

 

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 (NFS, ISCSI)

      • Native Backup v2016 Windows Server 2012R2 (NFS, ISCSI)