Deleting archives - VSOM 7.2

[jwood.ok]

Hello, we are in the midst of a long needed upgrade from VSOM 6.3 to 7.2 and soon on to at least 7.5.  We are currently on 7.2.  I have some media servers that I need to make some space on and I'm finding that it isn't as straightforward how to delete and archive on 7.2 either from VSOM or the VSM.  Could anyone point me in the right direction?

Thanks

[Nadeem Ahmed]

Hello John,

Yes certainly deleting Archives/Recording file is not easy way until you know the proper path to follow. Its never recommended to delete archives partially from CLI . Here is the procedure:-

1) first identify nos cameras recording needed and nos of camera do not.

2) you can delete those camera as full delete from VSOM which will delete the camera recording from Media along with camera however you can re-add those camera back again in VSM as just to free some space.

3) if you find recording is needed then you need to compress the archives/template setting like decreasing the number of days of retention of recording on server

I would suggest find camera which you do not require any longer ie recording then delete is full delete.

Regards

Nadeem

[jwood.ok]

Okay, basically what happened is that I think in the migration process, we had some archives that were orphaned.  I do not think they are tied to any cameras at this point.  Is the only way to delete those through the CLI?  I would imagine eventually they may fall off as the retention date is reached, but what if I wanted to get rid of them sooner?

[Nadeem Ahmed]

Hello John

What is the exact version of your VSM after upgrade? AFAIK there are some issue where archives retained on the server never get deleted.

Regards

Nadeem

[jwood.ok]

We are presently on 7.2.0

[Nadeem Ahmed]

Hello John,

I would advise to upgrade your VSM to 7.2.2 which is quite stable version and i am presuming that archives/recording which are not being deleted by system due to some issue. it will automatically truncated once upgrade completed successfully.

Meanwhile would you mind sending me the output one cli command

# ls -lrt

SSH to Media Server go to media paritions.

# ls -lrt

Regards

Nadeem Ahmed

[jwood.ok]

It looks pretty typical from what I can tell, here is an example from /media1:

-rw-rw-rw-  1 root root    0 Mar 30 04:23 systemstoragestatus
drwxrwxr-x  9 root root  130 Apr  4 12:03 1032
drwxrwxr-x  9 root root  130 Apr  4 12:03 1036
drwxrwxr-x  9 root root  130 Apr  4 12:03 1024
drwxrwxr-x  9 root root  130 Apr  4 12:03 1026
drwxrwxr-x  9 root root  130 Apr  4 12:03 1031
drwxrwxr-x 16 root root 4096 Apr  5 13:04 1039
-rw-rw-rw-  1 root root    0 Apr  6 03:43 getstoragestatus
drwxrwxr-x 10 root root  145 Apr  6 03:44 1020

[Nadeem Ahmed]

also where do you see orphaned archives? do you have any output?

Br,

Nadeem

[jwood.ok]

I see them in VSOM, they are listed as a_p_s1_<camera name>.

Can I ask you another question Nadeem?  I am guessing that template setting for "Verify Recording Space" cannot take into account motion archives, since it has no idea how much space they will take up.  Should I disable that setting on motion templates?  As is, it is preventing me from creating archives even though there is a good deal of space left.

[Nadeem Ahmed]

Yes you can disable it, if its causing to allocate spaces on Media server. When this feature is enable there are logical spaces reserved for camera added on VSOM whatever setting for camera recording configured in the template.

You can also calculate the future space which are reserved and actual consumed on media server from VSMC page.

Regards

Nadeem Ahmed