Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Backup Verification, MD5 Checksum

Discussion in 'Ideas' started by Paul Omans, Nov 8, 2017.

Backup Verification, MD5 Checksum 5 5 4votes
5/5, 4 votes

  1. Paul Omans

    Joined:
    Dec 2, 2016
    Messages:
    86
    Likes Received:
    36
    I have had several occurrences in the past few months where I make a backup, download the .zip file, and verify that I can open the .zip file without any issues (since if a .zip file is extremely corrupted, it won't even open), and restore it. The restore goes through correctly but when I start using the restored 3CX I am unable to register any new extensions (I can add new extensions but the phones themselves will not register), BLFs do not function reliably, and calls do not transfer reliably. This does not happen every time but it does happen occasionally. Even though I am making the backup, downloading the .zip file, and uploading it on different machines on different networks, the same issue has a chance of occurring, and has occurred in the past. This means it is not an issue with the specific machine or network I am uploading or downloading the backup from.

    To resolve this issue, all that 3CX needs to do is integrate some sort of MD5 verification (checksum) on the backup .zip file. This way, I will know 100% that the backup file does not contain any corrupted files (as even if the .zip file can be opened and browsed, there is a chance that one or two files did not backup properly inside of it). I realize that this would incur a high CPU usage, especially for large backups, but if verifying backups via hash/checksum was optional via check box, users with lower-power 3CX servers could leave it disabled.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. sd2

    sd2

    Joined:
    May 14, 2010
    Messages:
    1
    Likes Received:
    1
    This definitely needs to be implemented! Backups should be 100% solid 100% of the time without exception. We cannot be expected to do a test restore each week on every tenant we support to see if the backup is viable. Either an MD5 check or a fake restore to a temp instance on the same physical box to ensure the backup is usable. All these options should be available and the user should be able to enable or disable them depending on need.
     
    Paul Omans likes this.
  3. Paul Omans

    Joined:
    Dec 2, 2016
    Messages:
    86
    Likes Received:
    36
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...