Legal hold (litigation api) | NetApp | Page 1

lusty socket Jan 24, 2024, 10:05 AM

#

Hello, I have a demo environment on prem where I am trying to test the litigation endpoint using ONTAP rest api.

So far I am stuck with the configuration. At the moment I am getting this error message:
HTTPError('500 Server Error: Internal Server Error for url: https://x.x.x.x:443/api/storage/snaplock/litigations'): Audit logging is not configured for SVM "svm0".

I am trying to make an audit log configuration with the following command on the console:
DataONTAP9::> vserver audit create -vserver svm0 -destination /audit_vol/audit_log -rotate-size 100MB -rotate-limit 5

I get back this error:
Error: command failed: Failed to create audit configuration for Vserver "svm0". Reason: [Job 710] Job failed: Metadata verification failed. [Job 728] Job failed: Failed to create the volume on node "DataONTAP9-01". Reason: Request to create volume "MDV_aud_f4677e109c8f4725aed8970f855d46c0" failed because there is not enough space in aggregate "aggr0_DataONTAP9_01". Either create 1.68GB of free space in the aggregate or select a size of at most 341MB for the new volume.

Vserver details:
DataONTAP9::> volume show -vserver svm0
Vserver Volume Aggregate State Type Size Available Used%

svm0 audit_vol audit_aggr online RW 526.3MB 499.7MB 0%
svm0 svm0_root verba_aggr online RW 20MB 17.54MB 7%
svm0 verba_vol verba_aggr online RW 2.50GB 2.28GB 4%
3 entries were displayed.

Junction details:
DataONTAP9::> volume show -vserver svm0 -volume * -fields junction-path vserver volume junction-path

svm0 audit_vol /audit_vol
svm0 svm0_root /
svm0 verba_vol /verba_vol
3 entries were displayed.

What else should I check or provide?

fallow nebula Jan 24, 2024, 10:24 AM

#

[....]there is not enough space in aggregate "aggr0_DataONTAP9_01". Either create 1.68GB of free space in the aggregate
Free up some space in the aggregate and try again by either deleting volumes, resizing volumes (if they are thick provisioned) or deleting data or snapshots inside the other volumes (if they are thin provisioned)
You shouldn't fill up aggregates to the brim anyway, and if your aggregates have less than 2 gb of free space I guess you will soon run into lots of problems

lusty socket Jan 24, 2024, 10:30 AM

#

aggr0_DataONTAP9_01 is a ghost thing. I am not using that aggregate for nothing. But i am unable to delete it either because:

DataONTAP9::> volume delete -volume vol0 -vserver DataONTAP9-01
Error: command failed: This operation is not supported on 7-mode volume "vol0".

#

The strange thing for me is why does it want to use that aggregate? My volume is in another aggregate. It should use that, and there are plenty of space there.

fallow nebula Jan 24, 2024, 10:46 AM

#

lusty socket aggr0_DataONTAP9_01 is a ghost thing. I am not using that aggregate for nothing....

you're mixing volumes and aggregates. the vol0 you were trying to delete is probably the node root volume, you cannot delete that. But I don't know why it tries to use the root aggregate for auditing. Does the node 01 have a non-root aggregate anywhere? Or are aggregates only on node 02?

lusty socket Jan 24, 2024, 10:47 AM

#

This is a deployed .ova demo server

#

I think it only has 1 node

fallow nebula Jan 24, 2024, 10:48 AM

#

strange

lusty socket Jan 24, 2024, 10:49 AM

#

But i needed a vserver where snaplock is enabled. So i made a new aggregate, with 3 unassigned disks, then made a new vserver called svm0, then i added CIFS/SMB access, assigned a managament network interface for me to use my rest api with, and then i now need audit logging that fails.

#

I misht just redeploy and start from zero

#

I made the config a year ago with zero knowledge of what i am doing, just following snaplock guide online

#

The reason why I try to delete vol0 is this:

DataONTAP9::> storage aggregate delete -aggregate aggr0_DataONTAP9_01
Warning: Are you sure you want to destroy aggregate "aggr0_DataONTAP9_01"?
{y|n}: y
Error: command failed: Cannot delete an aggregate that has volumes. Delete or move the volumes and retry the command.

I cannot delete the aggregate until it has a volume. It has the ghost vol0 (whcih I cannot see on the UI)

fallow nebula Jan 24, 2024, 12:13 PM

#

I cannot delete the aggregate until it has a volume
no, you can only delete aggregates that have no volumes inside

It has the ghost vol0 (whcih I cannot see on the UI)
again, that is the root volume, you cannot see this and you cannot (must not) delete it

So, yes, you cannot delete the root aggregate (aggr0_DataONTAP9_01)

lusty socket Jan 25, 2024, 8:32 AM

#

I reinstalled the new ova demo system. Wrote down all the steps. It went well. However I would have a question.

#

I have a vserver with a volume which is shared via SMB. The vserver has a management network interface. I am unsure what user account I should use on the rest api:

cluster management ip + admin account seems to be okay except when I try to set litigation it fails due to missing vsadmin-snaplock login role
vserver management ip + snaplock_admin (which user is specific for the vserver? and has vsadmin-snaplock role). This seems to fail for other api calls sush as getting netapp version, other cluster information apis, but litigation works.
vserver management ip + vsadmin (which user is specific for the vserver? and has vsadmin role) This again fails with litigation api

Is there a way to setup a single user account to be able to use '/api/all' and litigation endpoint at the same time? Or do I have to configure multiple users for different endpoints?

#Legal hold (litigation api)