Jump to content
NAKIVO Community Forum

Leezy

Members
  • Posts

    35
  • Joined

  • Last visited

  • Days Won

    14

Leezy last won the day on April 26

Leezy had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Leezy's Achievements

Newbie

Newbie (1/14)

23

Reputation

  1. however there is still a missing link when comes to physical backup or proxmox VM backup. restoration only limited to vmware and hyperV. not other platform, that is why i have been asking for physical server or Bare metal restore options to be available. this would help us open up other market.
  2. the problem with Windows OS Antivirus with Nakivo backup repository files is still and issue. is there any roadmap that you guys will find ways to fix the repository files recognize as virus? putting exclusion list aside, we need to know which are the folders to exclude and process to exclude.
  3. does this means the KB article shown above is not valid? it does mention that it is supported for FTP backup.
  4. May i know if Basic License support single file restoration to email? i understand they dont support direct restoration, but does it support restore to email download?
  5. it would be great if KVM support of backup is made available to public. i think at the meantime, you could perform physical server backup for each VM running in the proxmox but limited to the supported OS version for each protected server.
  6. this link shows that ISCSI, NFS and FTP is supported. but how do it configure the FTP? https://helpcenter.nakivo.com/display/KB/Creating+a+Backup+Repository+on+NFS%2C+FTP%2C+or+iSCSI
  7. Does the NBR supports AHV community edition?
  8. is there any proper KB article that shows how to fix inconsistent repository. am getting following errors. [10/24 16:15:12.844] WRN: Backup repository with not finished consolidation... [10/24 16:16:07.801] LOG: Version 10.1.0.r47251 [10/24 16:16:07.935] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:16:08.105] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:16:08.177] WRN: Backup repository with not finished consolidation... [10/24 16:16:12.384] LOG: Version 10.1.0.r47251 [10/24 16:16:12.517] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:16:12.687] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:16:12.759] WRN: Backup repository with not finished consolidation... [10/24 16:17:07.857] LOG: Version 10.1.0.r47251 [10/24 16:17:07.990] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:17:08.178] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:17:08.248] WRN: Backup repository with not finished consolidation... [10/24 16:17:12.469] LOG: Version 10.1.0.r47251 [10/24 16:17:12.603] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:17:12.796] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:17:12.866] WRN: Backup repository with not finished consolidation... [10/24 16:18:08. 88] LOG: Version 10.1.0.r47251 [10/24 16:18:08.222] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:18:08.416] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:18:08.487] WRN: Backup repository with not finished consolidation... [10/24 16:18:12.689] LOG: Version 10.1.0.r47251 [10/24 16:18:12.822] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:18:12.993] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:18:13. 66] WRN: Backup repository with not finished consolidation... [10/24 16:19:07.927] LOG: Version 10.1.0.r47251 [10/24 16:19:08. 58] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:19:08.242] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:19:08.313] WRN: Backup repository with not finished consolidation... [10/24 16:19:12.531] LOG: Version 10.1.0.r47251 [10/24 16:19:12.665] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:19:12.829] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:19:12.902] WRN: Backup repository with not finished consolidation... [10/24 16:20:07.910] LOG: Version 10.1.0.r47251 [10/24 16:20:08. 42] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:20:08.225] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:20:08.296] WRN: Backup repository with not finished consolidation... [10/24 16:20:12.513] LOG: Version 10.1.0.r47251 [10/24 16:20:12.647] LOG: Backup repository "bh-mount/a767cdfc-a844-4abe-97b5-ea2819c2be5a/NakivoBackup": [10/24 16:20:12.822] DBG: Missmatching repository allocated size 628502294336 vs. 628502294216... [10/24 16:20:12.894] WRN: Backup repository with not finished consolidation... there should be some guide to perform the following fixing but there isn't. are there anyway we could try fixing it then going to the support every time?
  9. Hi nakivo, would you be by any way that nakivo console will be able to provide more logging during backup process. this helps us to read the logs so that we can try troubleshooting first. it would be nice to read the logs on nakivo or process during execute of backup of selected job. this can indicate that backup is running to certain steps and we can know where is the issue and etc. bottleneck monitoring would be great too... regards, zhiyuan
  10. there are 3 options for overwrite behavior. 1. rename if item exist 2. skip if item exist 3. overwrite the original if item exist can we request for few more possible options? 1. skip files older then specific date and also fix the "skip if item exisit" as the following option only compare with the folder name, it does not goes into the files if they exist. there should be an option to choose if skip folder if exist or skip files items if files items exist. that would be helpful for us to do recovery. thanks
  11. looks like we got Wasabi integration now... looking forward for S3 compatible storage
  12. i still had this issue ... the support told me to exclude the backup folder. but they still did not answer why the files was captured as false positive virus files....
  13. any one here get such alerts when using windows server 2019 as backup repo? it seems it only happens when i enable the repo as dedupe storage. else it will not show this... it will happen everytime i do a backup.
  14. the data are present in the vmdk. tested with another vm to view the data in it ... but not able to boot still... will try again later and update on result
  15. we actually failed the restore after exporting and importing back into datastore. the disk refuse to boot .... we are testing on Hyper-V image and export to VMDK, create a new vm server, upload disk vmware datastore, mount the disk and attempt to boot.
×
×
  • Create New...