Oracle ZFS Storage Appliance - SMU Cannot Delete a Snap Backup

Asset ID:	1-72-2147615.1
Update Date:	2018-01-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2147615.1 : Oracle ZFS Storage Appliance - SMU Cannot Delete a Snap Backup

Applies to:

Oracle ZFS Storage ZS4-4 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS4-4 - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

Oracle Snap Management Utility (SMU) version 1.2.2.2 & 1.3. Appliance is a cluster of ZS3-2 xxx03/xxx04.

An application needs to be removed from SMU.

First step is to remove the backup "20160225-1550-Online -After-RESTORE-12c" linked to this application.

When the snap backup is deleted, an error is displayed because SMU tries to delete snap backup on the incorrect ZFSSA cluster head.

--- TASK FAILED ---
Backup xxx:20160225-1450-Online-After-RESTORE-12c not on storage Sun ZFS Storage xxx04

Changes

With the SMU GUI, we can verify backup "20160225-1550-Online -After-RESTORE-12c" is on storage host xxx03.

With the ZFSSA BUI, we can verify snapshot "20160225-1550-Online -After-RESTORE-12c" is on share pool01/local/xxxx/arch & pool01/local/xxxx/data & pool01/local/xxxx/redo

Pool 'pool01' is currently imported on ZFSSA head xxx03.

Network modifications were done on the appliance few weeks ago.

Cause

In SMU code, SMU will try to find where the snapshot is located through the interface address defined in the remote share properties.

If the network address does not exist anymore, SMU does not know where to find the shares.

Here the storage xxx03 has the different network configuration after the snapshot has been created.

1> In the task output of snapshot creation:

START EXECUTE SCRIPT @ Thu Feb 25 14:48:31 WET 2016
STORAGE
xxx03
SCRIPT
addresses
END EXECUTE SCRIPT @ Thu Feb 25 14:48:48 WET 2016
OUTPUT
{"result":[{"addr":"xx.xx.xx.249","prefixLen":"25","admin":false},{"addr":"xx
.xx.xx.250","prefixLen":"25","admin":false},{"addr":"xx.xx.xx.125","prefixLen
":"25","admin":true},{"addr":"xx.xx.xx.64","prefixLen":"25","admin":true},{"ad
dr":"0.0.0.0","prefixLen":"8","admin":false},{"addr":"0.0.0.0","prefixLen":"8"
,"admin":false},{"addr":"0.0.0.0","prefixLen":"8","admin":false},{"addr":"0.0.
0.0","prefixLen":"8","admin":false}]}

2> In the task output of snapshot deletion:

START EXECUTE SCRIPT @ Tue May 31 10:30:23 WEST 2016
STORAGE
xxx03
SCRIPT
addresses
END EXECUTE SCRIPT @ Tue May 31 10:30:53 WEST 2016
OUTPUT
{"result":[{"addr":"xx.xx.xx.125","prefixLen":"25","admin":true},{"addr":"xx.xx
.xx.64","prefixLen":"25","admin":true},{"addr":"xx.xx.xx.3","prefixLen":"26",
"admin":false},{"addr":"xx.xx.xx.67","prefixLen":"26","admin":false},{"addr":"
xx.xx.xx.195","prefixLen":"26","admin":false},{"addr":"xx.xx.xx.131","prefixLe
n":"26","admin":false},{"addr":"0.0.0.0","prefixLen":"8","admin":false},{"addr
":"0.0.0.0","prefixLen":"8","admin":false}]}

The backup shares are mounted through IP xx.xx.xx.250.

SMU will try to find where the backup is located through the interface address xx.xx.xx.250.

Since this IP does not exist for xxx03, SMU does not know where to find the backup.

Solution

Temporarily assign IP xx.xx.xx.250 to xxx03 to enable deletion of the snap backup.

References

<BUG:23519511> - CANNOT REMOVE APPLICATION BECAUSE CANNOT DELETE SNAP BACKUPS ON ZFSSA

Attachments

This solution has no attachment