Yep, Collocation is enabled : 'Group' , hwever there are no Groups defined so it reverts to 'Node' as default I believe...
OK, here's where things look like they've gone wrong for these particular volumes..
They came up as 'EMPTY' when I did my cleanup of empty volumes on Friday.. however a stg pool backup cmd looks like it needed them..
-------------------- ---------------------------------------------------------
-------------------- ---------------------------------------------------------
01/20/2017 01:24:49 ANR1044I Removable volume D:\DEDUP\DEDUPVOL2666 is
required for space reclamation. (PROCESS: 3351)
01/20/2017 01:24:49 ANR8340I FILE volume D:\DEDUP\DEDUPVOL2666 mounted.
(PROCESS: 3351)
01/20/2017 01:24:49 ANR0512I Process 3351 opened input volume
D:\DEDUP\DEDUPVOL2666. (PROCESS: 3351)
01/20/2017 07:03:33 ANR1228I Removable volume D:\DEDUP\DEDUPVOL2666 is
required for storage pool backup. (SESSION: 713961,
PROCESS: 3362)
01/20/2017 07:04:20 ANR8340I FILE volume D:\DEDUP\DEDUPVOL2666 mounted.
(SESSION: 713961, PROCESS: 3362)
01/20/2017 07:04:20 ANR0512I Process 3362 opened input volume
D:\DEDUP\DEDUPVOL2666. (SESSION: 713961, PROCESS: 3362)
01/20/2017 07:31:37 ANR1228I Removable volume D:\DEDUP\DEDUPVOL2666 is
required for storage pool backup. (SESSION: 713961,
PROCESS: 3361)
01/20/2017 07:31:37 ANR8340I FILE volume D:\DEDUP\DEDUPVOL2666 mounted.
(SESSION: 713961, PROCESS: 3361)
01/20/2017 07:31:37 ANR0512I Process 3361 opened input volume
D:\DEDUP\DEDUPVOL2666. (SESSION: 713961, PROCESS: 3361)
01/20/2017 08:23:27 ANR1040I Space reclamation started for volume
D:\DEDUP\DEDUPVOL2666, storage pool DEDUPPOOL (process
number 3381). (PROCESS: 3381)
01/20/2017 08:23:27 ANR1044I Removable volume D:\DEDUP\DEDUPVOL2666 is
required for space reclamation. (PROCESS: 3381)
01/20/2017 08:23:27 ANR1176I Moving data for collocation set 1 of 1 on volume
D:\DEDUP\DEDUPVOL2666. (PROCESS: 3381)
01/20/2017 08:23:50 ANR8340I FILE volume D:\DEDUP\DEDUPVOL2666 mounted.
(PROCESS: 3381)
01/20/2017 08:23:50 ANR0512I Process 3381 opened input volume
D:\DEDUP\DEDUPVOL2666. (PROCESS: 3381)
01/20/2017 08:24:14 ANR0515I Process 3381 closed volume
D:\DEDUP\DEDUPVOL2666. (PROCESS: 3381)
01/20/2017 08:24:14 ANR1041I Space reclamation ended for volume
D:\DEDUP\DEDUPVOL2666. (PROCESS: 3381)
01/20/2017 12:24:23 ANR8340I FILE volume D:\DEDUP\DEDUPVOL2666 mounted.
(SESSION: 718053)
01/20/2017 12:24:23 ANR0511I Session 718053 opened output volume
D:\DEDUP\DEDUPVOL2666. (SESSION: 718053)
01/20/2017 12:25:41 ANR0514I Session 718053 closed volume
D:\DEDUP\DEDUPVOL2666. (SESSION: 718053)
01/20/2017 12:49:12 ANR2017I Administrator ADMIN issued command: DELETE
VOLUME D:\DEDUP\DEDUPVOL2666 (SESSION: 717442)
01/20/2017 12:49:13 ANR2406E DELETE VOLUME: Volume D:\DEDUP\DEDUPVOL2666
still contains data. (SESSION: 717442)
01/21/2017 06:49:48 ANR1228I Removable volume D:\DEDUP\DEDUPVOL2666 is
required for storage pool backup. (SESSION: 726532,
PROCESS: 3414)
01/21/2017 06:50:16 ANR1401W Mount request denied for volume
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 726532,
PROCESS: 3414)
01/21/2017 06:50:16 ANR1229W Volume D:\DEDUP\DEDUPVOL2666 is inaccessible
therefore it cannot be backed up to a copy storage pool
or copied to an active-data storage pool. (SESSION:
726532, PROCESS: 3414)
01/21/2017 06:50:18 ANR1401W Mount request denied for volume
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 726532,
PROCESS: 3414)
01/21/2017 06:50:18 ANR1229W Volume D:\DEDUP\DEDUPVOL2666 is inaccessible
therefore it cannot be backed up to a copy storage pool
or copied to an active-data storage pool. (SESSION:
726532, PROCESS: 3414)
01/21/2017 08:51:11 ANR1228I Removable volume D:\DEDUP\DEDUPVOL2666 is
required for storage pool backup. (SESSION: 726532,
PROCESS: 3414)
01/21/2017 08:51:11 ANR1401W Mount request denied for volume
more... (<ENTER> to continue, 'C' to cancel)
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 726532,
PROCESS: 3414)
01/21/2017 08:51:11 ANR1229W Volume D:\DEDUP\DEDUPVOL2666 is inaccessible
therefore it cannot be backed up to a copy storage pool
or copied to an active-data storage pool. (SESSION:
726532, PROCESS: 3414)
01/21/2017 16:01:28 ANR1401W Mount request denied for volume
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 731974)
01/21/2017 16:01:28 ANR1401W Mount request denied for volume
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 731974)
01/21/2017 16:01:28 ANR1401W Mount request denied for volume
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 731974)
01/21/2017 16:01:28 ANR1401W Mount request denied for volume
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 731974)
01/21/2017 16:01:28 ANR1401W Mount request denied for volume
D:\DEDUP\DEDUPVOL2666 - mount failed. (SESSION: 731974)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What I don't understand is that if you look at the cmd for the deletion of the volume it should not have touched it as it returned output to say it still contained data..?
Hence the reason I did not use the 'discarddata=y' afterwards for this very reason...
Can we get these FILE volumes back to their normal working state?