interrupted Vault backup

I have a working vault (TCL2) that cannot fully be backed up due to missing file.

Missing file is "C:\Program files\M-Files\Server vaults\TCL2\FileData\0\4\59\45973-1_1.bin"
How can I resolve this or a workaround to make a successful backup?
The Vault is otherwise working but without a back up I  have no at peace
I am on version 24.2.13421.8
Please help
Parents
  • You could try running the Verify and Repair operation in M-Files Admin and see if that helps.

    Sometimes for instance antivirus software may delete or move files, so if you have such scans running make sure the server vault directories are excluded as instructed in M-Files and Virus Scanning.

  • Thanks for your response. I used Verify and Repair but it did not help. 

  • I made another attempt today to run Verify and Repair. Below were the results:

    Error 1:
    The file size does not match the information in the database.
    File ID 45973, data file version 1. Object type 0, object ID 44732, object versions 1, 2.
    Delivery Note( DEL/21/01/30-0147)-ENKONAGROUP-2/6/2021.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44732-2?object=C207C4EF-B36B-400B-956F-11820D4EDA7D
    NOTE: M-Files cannot fix this error automatically.

    Error 2:
    The file size does not match the information in the database.
    File ID 45974, data file version 1. Object type 0, object ID 44733, object versions 1, 2.
    PRODUCTS CATALOGUE-.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44733-2?object=4831E7A8-6CAF-48CE-B1C3-F4E7C0630650
    NOTE: M-Files cannot fix this error automatically.

    Error 3:
    The file size does not match the information in the database.
    File ID 45975, data file version 1. Object type 0, object ID 44734, object versions 1, 2.
    Profoma Invoice(P09-2020)-ALFALAH-3/10/2020.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44734-2?object=21CFC03F-7C7E-4754-A2AB-72561AAD9D31
    NOTE: M-Files cannot fix this error automatically.

    Error 4:
    The file size does not match the information in the database.
    File ID 45976, data file version 1. Object type 0, object ID 44735, object versions 1, 2.
    PROFOMA CLEARING AGENT LETTER OF INTRO (SWISSPORT) (HAND HELD) (ID 2878).docx
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44735-2?object=382F0CF7-4F39-4452-AD28-850B789B739D
    NOTE: M-Files cannot fix this error automatically.

    Error 5:
    The file size does not match the information in the database.
    File ID 45977, data file version 1. Object type 0, object ID 44736, object versions 1, 2.
    Profoma Invoice(13170)-TIRA-10/23/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44736-2?object=838BB82B-293A-43A3-877C-D93DACE54E0E
    NOTE: M-Files cannot fix this error automatically.

    Error 6:
    The file size does not match the information in the database.
    File ID 45978, data file version 1. Object type 0, object ID 44737, object versions 1, 2.
    Profoma Invoice(13141)-SUMATRA-5/10/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44737-2?object=B2789973-030C-4513-9EC7-0D2630093CEE
    NOTE: M-Files cannot fix this error automatically.

    Error 7:
    The file size does not match the information in the database.
    File ID 45979, data file version 1. Object type 0, object ID 44738, object versions 1, 2.
    Profoma Invoice(13142)-SIHEBS-5/11/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44738-2?object=520D2B2C-5CAC-44EA-B849-CF4E616A6680
    NOTE: M-Files cannot fix this error automatically.

    Error 8:
    The file size does not match the information in the database.
    File ID 45980, data file version 1. Object type 0, object ID 44739, object versions 1, 2.
    Profoma Invoice(13155)-TFF-6/26/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44739-2?object=02FAA1B6-91F9-4E92-9511-2912E0545ED2
    NOTE: M-Files cannot fix this error automatically.

    Error 9:
    The file size does not match the information in the database.
    File ID 45981, data file version 1. Object type 0, object ID 44740, object versions 1, 2.
    Profoma Invoice(13155)-TFF-6/26/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44740-2?object=E3487693-0F2C-4F9B-8789-BBFEA83B757E
    NOTE: M-Files cannot fix this error automatically.

    Error 10:
    The file size does not match the information in the database.
    File ID 45982, data file version 1. Object type 0, object ID 44741, object versions 1, 2.
    Profoma Invoice(13160)-SUMATRA-7/17/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44741-2?object=7830070D-F01B-442B-8843-B512832C20E7
    NOTE: M-Files cannot fix this error automatically.

    Error 11:
    The file size does not match the information in the database.
    File ID 45983, data file version 1. Object type 0, object ID 44742, object versions 1, 2.
    Profoma Invoice(13162)-UNKNOWN-6/7/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44742-2?object=203CF3E1-C940-4173-B6DA-EC1072D0F91E
    NOTE: M-Files cannot fix this error automatically.

    Error 12:
    The file size does not match the information in the database.
    File ID 45984, data file version 1. Object type 0, object ID 44743, object versions 1, 2.
    Profoma Invoice(13162)-MAISHA-6/12/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44743-2?object=C4BCA366-C943-4A97-A0EC-A96BFEA74B57
    NOTE: M-Files cannot fix this error automatically.

    Error 13:
    The file size does not match the information in the database.
    File ID 45985, data file version 1. Object type 0, object ID 44744, object versions 1, 2.
    Profoma Invoice(13163)-TYCOON-6/13/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44744-2?object=D30D3611-9379-4E9B-8216-2080E40A40E5
    NOTE: M-Files cannot fix this error automatically.

    Error 14:
    The file size does not match the information in the database.
    File ID 45986, data file version 1. Object type 0, object ID 44745, object versions 1, 2.
    Profoma Invoice(13164)-TYCOON-6/13/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44745-2?object=34DF045A-72A2-4B65-883B-04E8DD335935
    NOTE: M-Files cannot fix this error automatically.

    Error 15:
    The file size does not match the information in the database.
    File ID 45987, data file version 1. Object type 0, object ID 44746, object versions 1, 2.
    Profoma Invoice(13165)-GIFRIMA-8/15/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44746-2?object=21C14E6C-AD8D-4A2B-9C45-07B9F9B37B93
    NOTE: M-Files cannot fix this error automatically.

    Error 16:
    The file size does not match the information in the database.
    File ID 45988, data file version 1. Object type 0, object ID 44747, object versions 1, 2.
    Profoma Invoice(13170)-WMA-9/19/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44747-2?object=0945CF9E-6FA3-4C1E-A022-5B6EC5C004F5
    NOTE: M-Files cannot fix this error automatically.

    Error 17:
    The file size does not match the information in the database.
    File ID 45989, data file version 1. Object type 0, object ID 44748, object versions 1, 2.
    Profoma Invoice(13182)-TAZARA-8/29/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44748-2?object=BB079512-E0B0-4328-90EF-11EE59967A98
    NOTE: M-Files cannot fix this error automatically.

    Error 18:
    The file size does not match the information in the database.
    File ID 45990, data file version 1. Object type 0, object ID 44749, object versions 1, 2.
    Profoma Invoice(13187)-BOT-11/5/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44749-2?object=9D59CFD2-AB9C-4729-B20A-F3AA63D0782C
    NOTE: M-Files cannot fix this error automatically.

    Error 19:
    The file size does not match the information in the database.
    File ID 45991, data file version 1. Object type 0, object ID 44750, object versions 1, 2.
    Profoma Invoice(13197)-TCDC-12/8/2018.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44750-2?object=8C42725A-FC6C-4788-8C9A-6AEF9AB196C0
    NOTE: M-Files cannot fix this error automatically.

    Error 20:
    The file size does not match the information in the database.
    File ID 45992, data file version 1. Object type 0, object ID 44751, object versions 1, 2.
    Profoma Invoice(2019021209/PF/0011)-SUMATRA-2/12/2019.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44751-2?object=43F1EA08-42FA-47D6-82FC-16F5D7CF9F0D
    NOTE: M-Files cannot fix this error automatically.

    Error 21:
    The file size does not match the information in the database.
    File ID 45993, data file version 1. Object type 0, object ID 44752, object versions 1, 2.
    Profoma Invoice(2019021416/PF/0016)-BONITE-2/14/2019.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44752-2?object=38248512-DC0F-4B39-A554-E2AD0F17EF69
    NOTE: M-Files cannot fix this error automatically.

    Error 22:
    The file size does not match the information in the database.
    File ID 45994, data file version 1. Object type 0, object ID 44753, object versions 1, 2, 3, 4.
    Profoma Invoice(2021101215/PF/1360)-MARIA AKONAAY-10/12/2021.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44753-4?object=5C20D165-38E9-4ADA-8554-0767ADA6D78B
    NOTE: M-Files cannot fix this error automatically.

    Error 23:
    The file size does not match the information in the database.
    File ID 45995, data file version 1. Object type 0, object ID 44754, object versions 1, 2.
    PROFOMAL INVOICE TO TRA (ID 2879).docx
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44754-2?object=D0B0CCF4-B45B-4CCA-A745-FB715B9CB1F8
    NOTE: M-Files cannot fix this error automatically.

    Error 24:
    The file size does not match the information in the database.
    File ID 45996, data file version 1. Object type 0, object ID 44755, object versions 1, 2.
    PROFOMAL INVOICE UPS (ID 2880).docx
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44755-2?object=C9FFC267-57F1-4A42-9983-00205C0362F4
    NOTE: M-Files cannot fix this error automatically.

    Error 25:
    The file size does not match the information in the database.
    File ID 45997, data file version 1. Object type 0, object ID 44756, object versions 1, 2.
    Profoma Invoice(P006-2022)-ALFALAH-1/6/2022.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44756-2?object=98A25908-7B2D-4E4F-86B5-E0DB30CA2267
    NOTE: M-Files cannot fix this error automatically.

    Error 26:
    The file size does not match the information in the database.
    File ID 45998, data file version 1. Object type 0, object ID 44757, object versions 1, 2.
    Profoma Invoice(P007-2022)-ALFALAH-1/6/2022.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44757-2?object=E9106CEB-F51B-4B50-AF85-445C8CA20892
    NOTE: M-Files cannot fix this error automatically.

    Error 27:
    A file does not exist on disk.
    File ID 45999, data file version 1. Object type 0, object ID 44758, object versions 1, 2.
    Profoma Invoice(P008-2022)-ALFALAH-1/6/2022.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44758-2?object=D8FDF11F-9930-4BFA-9635-915566E7A36E
    NOTE: M-Files cannot fix this error automatically.

  • As the user guide page linked above states, you should contact M-Files Support or your M-Files reseller if Verify and Repair finds errors it cannot fix automatically.

  • After going through the errors above I realised that they were due to the attempt I made to "fool" the system by renumbering the files from 45974 - 45999.to 45973 - 45998. Once I renumbered the files to their original number sequence now I just have the original error I reported.

  • Specifically the system says: 

    Error 1:
    A file does not exist on disk.
    File ID 45973, data file version 1. Object type 0, object ID 44732, object versions 1, 2.
    Delivery Note( DEL/21/01/30-0147)-ENKONAGROUP-2/6/2021.pdf
    m-files://show/8402010D-8244-4054-AB6A-3C19A24C82BF/0-44732-2?object=C207C4EF-B36B-400B-956F-11820D4EDA7D
    NOTE: M-Files cannot fix this error automatically.

    This file exists on a different Vault from where the current vault was copied. Is there a way I can still export it to the current Vault to solve the current problem?

  • As Joonas has said: if verify and repair cannot resolve the issues then you should liaise with support.

    That said: I would *strongly* advise you to not go altering values inside either the database or the file system.  Doing so will cause all sorts of potential long-term issues with which we would struggle to support you.

  • Thanks Craig. I will contact support. The warning is well taken.

Reply Children
No Data