Cannot delete SP DB Snapshots made to IBM COS.

[ThiagoM]

Hi,

I'm trying to delete a connection made from a IBM SP Server to IBM COS for a Proof of Concept activity but I'm stuck with a DB Snapshot test we've made. The volumes don`t seem to be deleted using delete volhistory command, so it won't let me delete the devclass nor the connection. There is no other storage pool, export or backupset using this device class.

The server was upgraded from 8.1.11 to 8.1.14 after the database snapshot was made.
Thank you in advance!

Protect: TSMSERVER1>q connection f=d

Connection Name Cloud Type Cloud URL Bucket Name Identity Key Source File Description
--------------- ---------- -------------------- ------------ ---------- ------------------------- -------------------------
POC_ACTIVITY S3 http://IP1|h- poc_activity xxxxxxxxx
ttp://IP2|h-
ttp://IP3

Protect: TSMSERVER1>delete connection POC_ACTIVITY
ANR3853E DELETE CONNECTION: Connection POC_ACTIVITY is in use by device class or storage pool CL-IBMCOS1-TSMSERVER1.
ANS8001I Return code 12.

Protect: TSMSERVER1>q devclass CL-IBMCOS1-TSMSERVER1 f=d

Device Class Name: CL-IBMCOS1-TSMSERVER1
Device Access Strategy: Sequential
Storage Pool Count: 0
Device Type: CLOUD
Format: DRIVE
...
WORM: No
...
Connection Name: POC_ACTIVITY
Cloud Storage Class: DEFAULT
Last Update by (administrator): ADMIN
Last Update Date/Time: 10/04/2022 03:34:15

Protect: S1TSVP04>delete devclass CL-IBMCOS1-TSMSERVER1
ANR2354E DELETE DEVCLASS: Device class CL-IBMCOS1-TSMSERVER1 is still referenced by one or more storage pools, or database backup, or export volumes or backupset volumes.
ANS8001I Return code 13.

Protect: TSMSERVER1>select cast(DATE_TIME as char(32)), cast(TYPE as char(12)),cast(DEVCLASS as char(32)),cast(VOLUME_NAME as char(96)) from volhistory where volume_name like '%.DSS%'

Unnamed[1] Unnamed[2] Unnamed[3] Unnamed[4]
--------------------------------- ------------- --------------------------------- -------------------------------------------------------------------------------------------------
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495729463899.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495763796400.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495797927788.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495832041455.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495865926322.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495899773011.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495933493877.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6495967531766.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496001395711.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496036301300.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496071061944.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496105359022.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496140125866.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496176574366.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496215898755.DSS
2022-04-10 03:42:26.000000 DBSNAPSHOT CL-IBMCOS1-TSMSERVER1 poc_activity/dbbackup-tsmserver1-92286bd1260411ec8b78f48e38d00b19/volumes/DSS/6496250041322.DSS

Protect: TSMSERVER1>delete volhist type=dbs todate=today-1

Deseja continuar? (Sim (S)/Não (N)) s
ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted.

Protect: TSMSERVER1>show versionhistory

Date (GMT) Version Pre-release Driver
-------------------- -------------------- --------------------
2021/10/05 17:49:01 8.1.11.000
2022/04/12 23:06:22 8.1.14.100

 

[erwanns]

Hello Tiago,
By default, you're not allowed to delete the latest DB Backup of each type (DBB or DBS).
Now, you have two options. You can either do a new DBS to another devclass. which will allow you to delete that one stored on COS, or you can use the undocumented force=yes option for the delete volhist command.