11-01-2011 06:33 AM
1) Warning (archive-sync) with server linux-efga:
The archive a_p_s1_22-041-Business_1_-_a_regular_50 doesn't exist in Media Server, deleted from VSOM.:
(occurred at 2011-10-31 12:30:59.0)
2) Warning (archive-sync) with server linux-efga:
The archive a_p_22-040-BusinessLab_1_-_a_regular_128_20111017161925 doesn't exist in Media Server, deleted from VSOM.:
(occurred at 2011-10-31 12:30:59.0)
had this happen to all archives on a server. Lost my history. Has anyone had this happen before.
Zack Suhre
11-01-2011 12:15 PM
I have seen this happen when the VSOM lost communication to the VSMS for extended periods of time.
11-04-2011 09:06 AM
VSOM is just a fancy UI and backend database that keeps track of everything done against the other services (VSMS, VSVM, etc...).
If I had to guess, I would say that someone manually perged the video archive data from the VSMS service itself and didn't use VSOM to do so, creating a consistency rift between the two.
11-08-2011 08:04 AM
I beleive Scott is right. Be aware, do NOT use VSOM to create, delete, or maintain your streams or archives. Do all that in the Broadware backend and then "Sync" the servers in VSOM.
11-08-2011 08:21 AM
hold'er... actually no. I'm not saying that at all. I believe that's how the disconnect occured in the first place (someone manipulated the archives or streams directly on the backend, without actually performing those tasks through VSOM).
It actually sounds as though someone either:
1 - Manually removed archives/streams from the VSMS instance /outside/ of VSOM.
2 - Perged or otherwise re-imaged the VSMS server wiping all the user data (less likely if the entire suite exists on the same MSP)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide