moon-buddy
ADSM.ORG Moderator
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
Node Name Type Filespace FSID Storage Number of Physical Logical
Name Pool Name Files Space Space
Occupied Occupied
(MB) (MB)
---------- ---- ---------- ---- ---------- ----------- ----------- -----------
NODE1 Bkup NODE1 - 1 WINTEL 102,077,914 299,290.78 297,285.78
\SystemS-
tate\NUL-
L\System
State\Sy-
stemState
So, no dedup data. I wanted to rule that out because the first node to do a backup will own the extents created. If a 2nd node does a backup and some extents are common to the 1st node, they are referenced. So when you delete the filespace for the 1st node, Q OCC still shows it, but as DELETED. That's because the node can't be deleted if it owns extents referenced by other nodes. This is NOT your case, so let's move on.
I'd try to delete that filespace again. Don't need to target that one specifically, just: DEL FI NODE1 *
Probably doesn't apply here, but since it's a quick check, it's worth a shot:
http://www-01.ibm.com/support/docview.wss?uid=swg21982493
Try to decommision the node in Spectrum Protect, before you decommision it, create a new domain that only has a default management class, and set the retention to 1 day. That way it should expire quick. Actually you could move to a new domain after decommissioning too.