OpenVDMv2 | Open Vessel Data Management v2 | Continuous Backup library
kandi X-RAY | OpenVDMv2 Summary
kandi X-RAY | OpenVDMv2 Summary
OpenVDMv2 is a ship-wide data management platform. It is comprised of a suite of programs and an accompanying web-application that provides vessel operators with a unified at-sea solution for retrieving and organizing files from multiple data acquisition systems into a unified cruise data package. Once the files are within the cruise data package they are immediately and safely accessible by crew and scientists. In addition OpenVDM can perform regularly backups of the cruise data package to one or more backup storage location/devices such as NAS arrays, external hard drives and even to shore-based servers. OpenVDMv2 includes a plugin architecture whereby vessel operators can develop and install their own data processing plugins used to web-based visualizations, perform data quality assurance (QA) tests and collecting data statistics at the file-level. In practice the output data from plugins is ~5% the size of the raw data files, making the architecture ideal for projecting situatitional off-ship to institute or cloud-based servers over low-bandwidth connections. OpenVDMv2 includes a hooks architure whereby vessel operators can link custom processes to run at key milestones during a cruise such as the start/end of a cruise, after a specific data transfer or after a data processing plugin completes. The allow vessels operators to design and deploy potentially very sophisticated and asynchronous data processing workflows. OpenVDMv2 includes full RESTful API, allowing vessel operators to build their own custom web-based and stand-alone applications that leverage information stored within OpenVDMv2 for their own, vessel-specific needs. Various UI refinements and bug fixes. Slight modification to the OpenVDM database schema for Cruise Data Transfers. Added support for vessel with dedicated vehicles such as ROVs and AUVs. This supoort includes the ability to define multiple lowerings within a cruise. Lowerings have their own ID, start and stop times. Collection System Transfers can be configured to save data on a cruise-basis or lowering basis. Added ability to define whether a the source directory for a collection system transfer from a local directory is a mount point. This is useful is the source directory is actually an externally connected device such as a USB HDD. Added ability to define whether a the destination directory for a cruise data transfer to a local directory is a mount point. This is useful is the destination directory is actually an externally connected device such as a USB HDD.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Create the message body
- Setup New Runner
- Dispatches the request
- Get human readable errors
- Get stats for a given data type
- Authenticate a user
- Short description of method testShipboard
- Generate pagination links
- Edit Ship - Transfer
- Renders a custom tab
OpenVDMv2 Key Features
OpenVDMv2 Examples and Code Snippets
Community Discussions
Trending Discussions on Continuous Backup
QUESTION
ANSWER
Answered 2022-Feb-22 at 10:59I am not sure if you have seen this message in the portal when you created the account/also mentioned in the doc
"You will not be able to switch between the backup policies after the account has been created"
since you need to select either "Periodic" or "Continuous" at the creation of Cosmos Account, it becomes mandatory.
Update:
You will not see the above in portal anymore, you can Switch from "Periodic" to "Continous" on an existing account and that cannot be reverted. You can read more here.
QUESTION
What would be the consistency of the continuous backup of the write region if the database is using bounded staleness consistency? Will it be equivalent to strong consistent data assuming no failovers happened?
Thanks Guru
...ANSWER
Answered 2021-Nov-25 at 17:15Backups made from any secondary region will have data consistency defined by the guarantees provided by the consistency level chosen. In the case of strong consistency, all secondary region backups will have completely consistent data.
Bounded staleness will have data that may have stale or inconsistent data inside the defined staleness window (minimum 300 seconds or 100k writes). Outside of that staleness window the data will be consistent.
Data for the weaker consistency levels will have no guarantees for consistency from backups in secondary regions.
QUESTION
MongoDB has deprecated the continuous back up of data. It has recommended using CPS (Cloud provider snapshots). As far as I understood, snapshots isn't really going to be effective compared to continuous backup coz, if system breaks, then we can only be able to restore the data till the previous snapshot which isn't gonna make the database up-to-date or close to it atleast.
Am I missing something here in my understanding?
...ANSWER
Answered 2020-May-19 at 10:12Cloud provider snapshots can be combined with point in time restore to give the recovery point objective you require. With oplog based restores you can get granularity of one second.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install OpenVDMv2
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page