Direkt zum Inhalt

vmprotect-online v9 robustness

Thread needs solution

It would be helpful to have a sense of how robust the AVMP-online system is - in particular:
if a transmission is interrupted, is the online database (maybe I should say backup file, but this contains many backups, so seems more like a database) recoverable?
If a copy job is canceled, what happens to the online database?
If an online copy fails, and I restart, is the online database probably fine?
Does online database maintenance remove partial transfers?
What is the likelihood that the online backup file becomes corrupt and must be purged and recreated?
Is there documentation on this system? Probably easily found, but I am coming up empty.

I have set up my first implementation of VMprotect v9/online. a number of attempts at the first replication failed, to a variety of problems - WAN, complaints of network slowness during the initial replication that required me to cancel the copy, one write failure. I was frustrated to find that there is no provision for bandwidth management within the VMProtect product, nor for suspending or holding a copy operation. Deleting the copy job is not a great solution when simply looking to hold the job for a period of time (like until the start of the weekend).

I am now controlling outbound load for VMProtect-online at the firewal - that is working - and now I need to understand the impact of the past week on the online backup files.

Thanks

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 22
Kommentare: 3800

Hi Munir,

If the data transmission to online is cancelled then these chunks are not considered as valid ones and become subject to deletion. This deletion is performed on the background on the servers side (so-called "sparse" process), once the client side detects incomplete chunks. Upon next backup these incomplete parts are skipped and not taken into consideration. The online "database" is designed to survive through such cancellations (or failures due to network outage for example) without corruption of the backups.

On the backend (online servers side) there is a set of "front-end" servers (so-called FES) which serve the clients request and redirect the datatransfers to the actual storage servers. Each backup is distributed among multiple storage servers and duplicated to ensure the safety of the data (so even a complete loss of one storage server does not cause archive corruption for the end users). If connection to one FES server fails for whatever reasons the client side tries to re-connect to another FES automatically in order to continue.

P.S. yes there is currently no bandwidth control option in vmProtect 9 and we plan to add it into the 10th version (similar to the option we have in Acronis Backup and Recovery 11.5 product line).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager