VSOM Missing Archives

[Reid Ditzler]

My customer is on the highest firmware of VSOM/VSMS (6.3.2) and I configured all the archives (86) to run for 30 days and shelve that archive for another 30 days, giving the customer 2 months worth of backups at all times. Once all configurations were finished everything looked correct but when I went onsite and I saw that 6 are now missing. It has only been 2 weeks since I made this change. When I try to re-add the archive I get the error that there isn't enought space but there is over 4TB remaining.

Has anyone else come across this issue, or recommend a different schedule?

The customer has stated that they want the cameras to run 24/7 and have a least 1 month of backups at all times

Thanks in advance  

[Holly Goguen]

HI Reid,

How are your archives configured  ? (medaia type, f/b rate/quality)

How many media servers do you have ?

Are you using a separate back up server for the 30 days after the loop?
How much total drive space for archives is available ?

~Holly

[Reid Ditzler]

To answer your questions in order:

     -The cameras are configured as MPEG-4 and the frame rate is at the highest it could go. I forget the setting, I didn't          configure the cameras.

     -There is one media server

     -No all backups are stored on the VSMS

     - Not Sure the total amount but after 77 are running my associate onsite can see that 4TB of space is remaining.

[Holly Goguen]

Hi Reid,

I'm assuming that you mean that you've configured a 30 day loop and a 30 day back up

If that's the case:

-86 cameras (total)

-and are essentially saving 60 days worth of data

-MPEG, 4Cif, and at 2000 Kbps (i didn't bother calculating for anything higher)

you would need:

107 TB

If you mean that you set a 30 day loop, with an expiration of 30 days (the expiration kicks in ONLY after an archive has been stopped/shelved)

Then you would need about 54 TB

What size server and what size drives do you have?

The TB available that you see on the server is literal.  How much you've stored and how much is left.

When you look at that page it does not take into consideration what you set your loops, backups or expiration dates to.

~Holly

[jcbbcj]

Hi Reid,

We too have had some video streams go missing.  We are running 6.3.2 and have our cameras set to archive to Record on Motion (ROM) loops.  We have two camera feeds now that have a large 7-hour window of time missing.  We have a TAC open and have CISCO looking for a reason.  We have good video before and after the missing timeslot.  We had not power loss, runtime on all equipment including the network layer was up for that period of time.  It is strange that it just disappeared.   We are still researching but I can confirm that 6.3.2 did miss or lose some data.  

-JB

[Zack Suhre]

We have had the same problem.  we are troubleshooting by turning off the record on motion for a few days to see if it will make a difference.  The weirdest this we have come accross is we had a three hour portion of an archive go missing.  it was there and we made a clip and went back to expand the clip and the archive was not availble for this time.  this is a huge problem for us because we rely on that video for most of what we do.  any help would be greatly appriciated.  I also think 6.3.2 vsom is just having issues constantly.

[Holly Goguen]

Hi JB and Zack,

If you normally have constant activity in areas for more than 2 hours where you are using motion detection, you need to make sure that you change the Maximum Event Marking Duration setting to the longest expected time of continuous activity.  The default is 7200 seconds (2 hours)

This is a setting on the Media Server section of the Management Console (VSMC page)

/vsmc   -> Media Server -> scroll to the bottom of page

Events

Maximum Event Marking Duration:

The value should be entered in seconds and the range of values is between (1-86400)

You would need to change this setting on any media server where you are using motoin and continuous movement is over 2 hours on any camera/archive associated with that media server.

After the setting is changed, the media swerver software needs to be restarted:

/etc/init.c/cisco restart

Hopefully this helps.

If you're sill having issues, please feel free to ask any quesions, or open a TAC case and report back here with the SR number.

~Holly

[asadabbasrizvi]

hey , i am getting endpoint error. i am using bosh autodome cams on vsom and unable to get the view.

Problem: Unable to view Bosh auto dome 300 on to the VSOM.

Error Message displayed: Endpoint Error: Cam Unreachable.

Software Versions: VSMS 6.3.1 VSOM 6.3.1, Camera Firmware 3.52

Problem Description: Unable to view camera on VSOM and it can be viewable on web. i am having 40 bosh auto dome cameras and 6 of them are showing error “Endpoint Error: Cam unreachable”. This failure is only for 6 cameras. I tried removing/adding the camera several times but it did not help. Also tried restarting both the camera and VSMS server, no improvement

SYSTEM LOG

2011-09-30 06:23:48.268 [ httpd(4065) FE_COMMANDER=1

] p_ptz_3 Started Successfully!
2011-09-30 06:23:48.655 [ proxy(4759).p_ptz_3 BE_PROXY=1 ] Proxy args: proxy p_ptz_3 1317345828_635620
2011-09-30 06:23:48.656 [ proxy(4759).p_ptz_3 BE_PROXY=1 ] setup.alias: p_ptz_3 setup.modelName: bosch_autodome_300
2011-09-30 06:23:48.691 [ proxy(4759).p_ptz_3 BE_PROXY=1 ] >>> Entering Proxy::run() for proxy='p_ptz_3'
2011-09-30 06:23:48.691 [ proxy(4759).p_ptz_3 BE_PROXY=1 ] nrservers = 1000, nrclients = 1000, num_clients = 2
2011-09-30 06:23:48.691 [ proxy(4759).p_ptz_3 IL_SHMEM=1 ] keym = 1862361302 keys = 1996579030 shmid = 851975 semid = 294917
2011-09-30 06:23:48.691 [ proxy(4759).p_ptz_3 IL_SHMEM=1 ] keym = 3707855063 keys = 3791741143 shmid = 884744 semid = 327686
2011-09-30 06:23:48.692 [ proxy(4759).p_ptz_3 IL_SHMEM=1 ] keym = 687956184 keys = 771842264 shmid = 917513 semid = 360455
2011-09-30 06:23:48.701 [ proxy(4759).p_ptz_3 IL_SHMEM=1 ] keym = 2265014489 keys = 2365677785 shmid = 950282 semid = 393224
snmpd:/usr/BWhttpd/sbin/snmpd:status...Stopped
snmpd:/usr/BWhttpd/sbin/snmpd:status...Started

[sfeldmann]

Holly, can you please clarify this with the 2 hour activity window?  What happens if there IS activity over that defined window, and when are the files tagged for activity?  Is it only after the stop event and only if the stop event happened within that window?  I would think that it should be programmed such that if a stop event wasnt recieved at the end of the window, it should act as if there was a stop event at that time, and then a new start event.  This would ensure that there was no loss on the motion recordings.  I can think of many scenarios where you would have slow traffic, but then for one reason or another lots of sustained motion.  It is at these times where you probably want the archives the most.  I can increase the timer to the max, but again, what happens if motion lasts for more than a day.  What are the negatives about the increased timer?