Version 18.0
May 17, 2023
Release Overview
The new features:
Epic/Module | Story/Task | Description |
Masking integration | Implement Masking parameters for Virtualization | |
Masking integration | Provide information about masking for snapshot operations | |
Self-service deploy | Install source and target linux agents as executable | |
Self-service deploy | Initial self-service deployment for Oracle RMAN GI | |
Masking integration | Mask VDB with already existing Masking configuration | |
Masking integration#2 | Redirect Virtualization user directly from VDB instance to Masking tool | |
Self-service deploy | Ability to use source host as target host | |
VDB Management | Show only relevant DB homes in Create VDB/Start VDB screens | |
Share | Add block for sharing snapshot if reciever hasn't access to the owner's dst-agent |
The list of known issues found during the last release:
Issue key | Summary |
LOKI-2070 | IM/LOKI Integration. Linked data isn't removed after rollback to non-masked snapshot |
LOKI-2069 | VDB management. Cannot read properties of undefined (reading 'id') after try to delete snapshot |
LOKI-2068 | IM/LOKI Integration. DS and env isn't removed after remove VDB |
LOKI-2066 | VDB management. Remove masking button is shown for VDB after remove related Datasource and Environment in masking |
LOKI-2065 | Only on loki_for_pm env. VDB management.Error "Client failed to createMaskingDataSource. Response code: 400, response message: Impossible to create the DataSource with existed name Virtualization VDB Clone1" |
LOKI-2029 | VDB can not be removed due to busy volume of zfs |
LOKI-2011 | VDB management. Delay for button set update during activation LIVE GI |
LOKI-2010 | Error Client '' failed to startMaskingSensitiveSearch. after try to start masking process on redeployed LOKI env |
LOKI-2005 | IM/LOKI Integration. Masking status bar isn't shown after refresing page |
LOKI-2004 | VDB management. MSSQL 2016 Native NFS. VDB failed with error: 'Directory '\\172.31.4.253\main_pool\00000497\' does not exists' (same host) |
LOKI-2003 | VDB management. MSSQL LIVE. 'Failed to start MSSQL VDB with error: null' (same host) |
LOKI-1991 | VDB Management. MSSQL 2019. Different VDBs from different TDEs do not start at the same time on different DB Homes |
LOKI-1990 | Source Management. RMAN DB 19 shows incorrect TDE version |
LOKI-1985 | Handle block_change_tracking oracle setting when starting / stoping VDB |
LOKI-1974 | When starting VDB from LiveGI on Oracle 11, the orapwd fails |
LOKI-1973 | orapwd result is not checked |
LOKI-1960 | VDB Management. RAC-to-RAC. Can't start VDB with field "Ora SID" from numbers |
LOKI-1946 | VDB Management. Can't edit any volume |
LOKI-1935 | Scheduled automatic GI refresh does not run after GI creation finishes. |
LOKI-1905 | VDB management. Incorrect message for LiveGI creation if main pool is absent |
LOKI-1901 | VDB Management. RMAN GI. After the volume is created, the snapshot is automatically deleted(floating bug) |
LOKI-1899 | VDB Management/Source Management. The dbSid value is present in code for PG on MSSQL |
Testing status:
The regression tests - completed
https://docs.google.com/spreadsheets/d/18JXYqfgl0T6KtpWdrR6W9JAlS5I9jA1Z/edit?pli=1#gid=1742277043
The LOKI/Masking integration tests - completed
https://docs.google.com/spreadsheets/d/1k-fNqCiR2hLCVtWnRdDAmWZv6xkQzkJb2L5OCcMTZ-w/edit#gid=0
No critical bugs were found during the regression testing.
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 (NFS, ISCSI)
Native Backup v2016 (NFS, ISCSI)
LIVE v2019 (NFS, ISCSI)
Native Backup v2019 (NFS, ISCSI)