NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

Data Protection

SnapCenter Plugin for vSphere 4.1.1 no REST API"Cleanup"

SimsonChan
5,003 Views

One of my client they removed a mounted cloned LUN on vCenter mistakenly. That LUN of-course created via SCPVS 4.1.1.

Now, the task still show on SCPvS and status is Mounted. 

I tried to follow official KB attempt to clean this entry on SCPvS console. The KB as below.

===================================================

Cannot unmount a backup
Description
Although the backup is listed as mounted in the SnapCenter VMware vSphere web client GUI,
it is not listed in the unmount backup screen.
Workaround
Use the REST API "/backup/{backup-Id}/cleanup" to clean up the out-of-bound datastores. 

===================================================

 

However, I cannot find parameter  "cleanup" there. Only DELETE, GET, PUT options there. Is it "cleanup" missed? Or any privilege required for this?  

 

Anyone have idea for this? 

1 ACCEPTED SOLUTION

pranjith
4,863 Views

Please use the Datastore section there.Delete.PNG

View solution in original post

4 REPLIES 4

pranjith
4,948 Views

Hi,

 

Can you try the rest API for datastore for the same:


DELETE   /datastores/{backupId}/cleanup ==>Cleanup out of band deleted datastores of a backup

SimsonChan
4,934 Views

There has no such cleanup under {backupId}. even tired to input "'cleanup" manually

 

WhatsApp Image 2020-07-29 at 12.58.43 PM.jpeg

pranjith
4,864 Views

Please use the Datastore section there.Delete.PNG

SimsonChan
4,809 Views

Seems worked! Many thanks. The record on SCPV released now.

Do you have any idea the "cleanup" why ain't located in the place official KB mentioned? 

I believe it placed correctly on newer version. 

Public