Jump to content
v10.11.2 Is Here: Free Agent-Based Backup for Proxmox and More! ×
NAKIVO Community Forum

Leezy

Members
  • Posts

    37
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by Leezy

  1. @Official Moderator will there be an alternative option to drop down select for s3 compatible? so we can key in the s3 compatible object storage address and other information without us having to use only wasabi and AWS as the only option?
  2. AP southeast 1 missing from the drop down list. how can i get it ?
  3. 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.
  4. 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.
  5. does this means the KB article shown above is not valid? it does mention that it is supported for FTP backup.
  6. 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?
  7. 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.
  8. 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
  9. Does the NBR supports AHV community edition?
  10. 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?
  11. 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
  12. 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
  13. looks like we got Wasabi integration now... looking forward for S3 compatible storage
  14. 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....
  15. 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.
  16. 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
  17. 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.
  18. Hi support, is there anyway we can do cross platform restore without having to export? it is waste of time when come to cross platform from VHDX if we have to export into VMDK before upload back into the Datastore to boot up. i understand we have NFS option and CIFS option, but it would be useful if we could upload directly into Datastore on Vmware. can we request for this features?
  19. can i do flash reboot on repository which are not compressed and deduplicated backups? or from dedupe appliance?
  20. i did not enable the compression and dedupe on the NBR. we only configure the windows server with dedupe on the following volume. it does looks food on the result. only different is that we do not have the option do continues backup.
  21. if any of you guys planning to use dedupe on windows server 2019, here is some results i am getting during the backup. i have configure my server to backup without compression and dedupe enable, and with dedupe appliance option enable. here is some interesting results to share. not sure is this the best result i can get on windows server deuplication comparing it to built in dedupe. both runs using post processing deduplication.
  22. Hi, would like to know is there any best practices if we enable deduplication on backup repository on windows server? are there any benefits if we store data into \windows server and run deduplication on it? do you have any best practices for this? thanks.
  23. what is the recommended Disk Reclamation schedule? how frequent do we run? i have near 1TB space to reclaim at offsite and we found out that each time we do space reclaim, the process will takes about 2-3 days. it is quite painful when we dealing with large data size. are there any specific recommendation to deal with this ?
  24. maybe this is the design you looking for. correct me if im wrong....
  25. i would like to know if we configure AWS S3 as target repository. during backup, or backup copy job, does the transporter store local copy before uploading to AWS? or it will directly upload to S3? will there be a local cache copy during S3 transmission?
×
×
  • Create New...