Yes I did. Following the instructions, I did the MARKDAMAGED and
REMOVEDAMAGED. I just ran it again:

8:13:16 PM   WIND : delete stgpooldirectory containerstgpool
/powervault_recover_pool
ANR3646E DELETE STGPOOLDIRECTORY: Storage pool directory
/powervault_recover_pool has an access mode of DESTROYED and has active
data.
ANS8001I Return code 27.

MARKDAMAGED
-----------------------
08/11/2021 20:13:24  ANR2017I Administrator ZFORRAY issued command: AUDIT

                      CONTAINER STGPOOL=containerstgpool ACTION=markdamaged

                      (SESSION: 871)

08/11/2021 20:13:24  ANR0984I Process 63 for AUDIT CONTAINER started in the

                      BACKGROUND at 08:13:24 PM. (SESSION: 871, PROCESS:
63)
08/11/2021 20:13:24  ANR0405I Session 871 ended for administrator ZFORRAY

                      (WinNT). (SESSION: 871)

08/11/2021 20:13:24  ANR0984I Process 64 for AUDIT CONTAINER (MARK DAMAGED)

                      started in the BACKGROUND at 08:13:24 PM. (SESSION:
871,
                      PROCESS: 64)

08/11/2021 20:13:24  ANR4894I Audit Container (Mark Damaged) process
started
                      for container
/powervault_recover_pool/00/00000000000000-
                      0a.dcf (process ID 64). (SESSION: 871, PROCESS: 64)

08/11/2021 20:13:24  ANR0984I Process 65 for AUDIT CONTAINER (MARK DAMAGED)

                      started in the BACKGROUND at 08:13:24 PM. (SESSION:
871,
                      PROCESS: 65)

08/11/2021 20:13:24  ANR4894I Audit Container (Mark Damaged) process
started
                      for container
/powervault_recover_pool/00/00000000000000-
                      22.dcf (process ID 65). (SESSION: 871, PROCESS: 65)

08/11/2021 20:13:24  ANR4891I AUDIT CONTAINER process 65 ended for the

                      /powervault_recover_pool/00/0000000000000022.dcf

                      container: 0 data extents inspected, 0 data extents

                      marked as damaged, 0 data extents previously marked
as
                      damaged reset to undamaged, and 0 data extents marked
as
                      orphaned. (SESSION: 871, PROCESS: 65)

08/11/2021 20:13:24  ANR0985I Process 65 for AUDIT CONTAINER (MARK DAMAGED)

                      running in the BACKGROUND completed with completion

                      state SUCCESS at 08:13:24 PM. (SESSION: 871, PROCESS:
65)
08/11/2021 20:13:24  ANR4891I AUDIT CONTAINER process 64 ended for the

                      /powervault_recover_pool/00/000000000000000a.dcf

                      container: 0 data extents inspected, 0 data extents

                      marked as damaged, 0 data extents previously marked
as
                      damaged reset to undamaged, and 0 data extents marked
as
                      orphaned. (SESSION: 871, PROCESS: 64)

08/11/2021 20:13:24  ANR0985I Process 64 for AUDIT CONTAINER (MARK DAMAGED)

                      running in the BACKGROUND completed with completion

                      state SUCCESS at 08:13:24 PM. (SESSION: 871, PROCESS:
64)
08/11/2021 20:13:24  ANR4013I Audit container process 63 completed audit of
2
                      containers; 2 successfully audited containers, 0
failed
                      audited containers. (SESSION: 871, PROCESS: 65)

08/11/2021 20:13:24  ANR0987I Process 63 for AUDIT CONTAINER running in the

                      BACKGROUND processed 2 items with a completion state
of
                      SUCCESS at 08:13:24 PM. (SESSION: 871, PROCESS: 65)


REMOVEDAMAGED
----------------------------
08/11/2021 20:14:11  ANR2017I Administrator ZFORRAY issued command: AUDIT

                      CONTAINER stgpool=containerstgpool
action=removedamaged
                      (SESSION: 876)

08/11/2021 20:14:11  ANR2017I Administrator ZFORRAY issued command: AUDIT

                      CONTAINER STGPOOL=containerstgpool
ACTION=removedamaged
                      (SESSION: 876)

08/11/2021 20:14:11  ANR0984I Process 66 for AUDIT CONTAINER (REMOVE
DAMAGED)
                      started in the BACKGROUND at 08:14:11 PM. (SESSION:
876,
                      PROCESS: 66)

08/11/2021 20:14:11  ANR4889I Audit Container (Remove Damaged) process
started
                      for storage pool CONTAINERSTGPOOL (process ID 66).

                      (SESSION: 876, PROCESS: 66)

08/11/2021 20:14:11  ANR0405I Session 876 ended for administrator ZFORRAY

                      (WinNT). (SESSION: 876)

08/11/2021 20:14:22  ANR3729I The AUDIT CONTAINER command process 66

                      completed: 48895 damaged objects are deleted. 0
damaged
                      objects are skipped. 0 orphan objects are deleted in

                      cloud-container storage pools. 0 orphan objects are

                      skipped in cloud-container storage pools.  (SESSION:

                      876, PROCESS: 66)

08/11/2021 20:14:22  ANR0987I Process 66 for AUDIT CONTAINER (REMOVE
DAMAGED)
                      running in the BACKGROUND processed 48,895 items with
a
                      completion state of SUCCESS at 08:14:22 PM. (SESSION:

                      876, PROCESS: 66)


DELETE
-----------
8:17:39 PM   WIND : delete stgpooldirectory containerstgpool
/powervault_recover_pool
ANR3646E DELETE STGPOOLDIRECTORY: Storage pool directory
/powervault_recover_pool has an access mode of DESTROYED and has active
data.
ANS8001I Return code 27.


On Wed, Aug 11, 2021 at 6:15 PM Richard van Denzel <rvanden...@gmail.com>
wrote:

> Hi Zoltan,
>
> Have you tried AUDIT CONTAINER with ACTION=REMOVEDAMAGED?
>
> Richard
>
> Op do 12 aug. 2021 00:06 schreef Zoltan Forray <zfor...@vcu.edu>:
>
> > After spending 3-months recovering from a Powervault crash (multiple disk
> > and array) since everything was deduped, the suggestion was to move to
> > Containers since the recovery would have been easier.
> >
> > We realize that Directory Containers on V7 are mostly a "black hole" and
> we
> > don't plan to start using them until we upgrade everything to V8.  Since
> > the failed PV has been repaired/rebuilt and was empty, we decided to get
> > some experience with Containers and created one on it and a Directory to
> > use the PV space. Used my desktop to backup to it and all was well.
> >
> > Now that we are done, we can't figure out how to get rid of the directory
> > and container.  I deleted all backups for the node and the node itself. I
> > have been following these instructions (
> >
> >
> https://www.ibm.com/docs/en/spectrum-protect/8.1.0?topic=commands-delete-stgpooldirectory-deleting-storage-pool-directory
> > )
> > but it still says:
> >
> > ANR3646E DELETE STGPOOLDIRECTORY: Storage pool directory
> > /powervault_recover_pool has an access mode of DESTROYED and has active
> > data.
> > ANS8001I Return code 27.
> >
> > What am I missing?
> >
> > --
> > *Zoltan Forray*
> > IBM Spectrum Protect Administrator
> > VMware Administrator
> > Virginia Commonwealth University
> > UCC/Office of Technology Services
> > www.ucc.vcu.edu
> > zfor...@vcu.edu - 804-828-4807
> > Don't be a phishing victim - VCU and other reputable organizations will
> > never use email to request that you reply with your password, social
> > security number or confidential personal information. For more details
> > visit http://phishing.vcu.edu/
> > <https://adminmicro2.questionpro.com>
> >
>


--
*Zoltan Forray*
IBM Spectrum Protect Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://phishing.vcu.edu/
<https://adminmicro2.questionpro.com>

Reply via email to