Jump to content
NAKIVO Community Forum

Leaderboard

Popular Content

Showing content with the highest reputation since 04/13/21 in Posts

  1. In a multi-tenant environment, if vpn drops for any reasons (isp problem, customer's ac problem, etc) the sheduled jobs will start in time or they will wait director command to start? thank's and best regards
    2 points
  2. Hi. have been using Nakivo for over 5 years. Has anyone else had issues with the 10.3 update on Synology NAS units? First after upgrading the certificates for the transporters would not work and I had to rename them. Now my offisite transporter on my offsite NAS units will not accept connections on 9446. i am stuck with no off site backups. yes I have a ticket open but looking for feedback form the community. I do not want to go all weekend without offsite backups
    1 point
  3. @Mark Please keep the forum updated, if you have any news. reclaim is one of the biggest pain in my point of view at the current status of nakivo.
    1 point
  4. Our space reclaim we run each week, but never get past about 57-58% before stopping for weekend backups and copies offsite, then starting again the next week. Could we administratively allocate more processing resources for the space reclaim to get further at least once, then return them to default? This is running on a Synology NAS.
    1 point
  5. that was done this morning with link to URL of this discussion in summary as well as the question that started this
    1 point
  6. Hi. The problem is not with the certificates anymore. The offsite transporter and repository are not accessible from the On Site Synology NAS install. The connection to "X.X.X.X:9446" was refused. Make sure the provided information is correct and the connection is not blocked. I have setup a Telnet session and can successfully connect to that IP form my onsite network using port 9446 I have a ticket open but they have told me it is off to development to work on the issue. I currently have no offsite backups and entering my 2nd week.
    1 point
  7. Hi Jason I'm still on 10.2, so I can't help with your issue... Did you get solution from support? I also use Synology and like to know if it's a showstopper. Thanks Mario
    1 point
  8. Hello! Just wanted to know what differentiates NAKIVO from the competence solutions? Because frankly, everything seems pretty similar.
    1 point
  9. Doesn't Microsoft 365 back up the data? Why do you even need another solution for that?
    1 point
  10. Hello, @lionking62! We are planning to support Ubuntu 20.04 in NBR v10.4. The release is planned for July 2021. Please find the extended Linux OS support list for it: Ubuntu 20.04, RHEL7.6/7.7/8.0/8.1/8.2, SLES15/CentOS 8 As for now, you can upgrade OS Ubuntu to v18.04 which is currently supported as well.
    1 point
  11. The data sheet for VMware Backup and Replication 10.3 and the Supported Platforms section of the User Guide both list "Ubuntu 16.04–18.04 Server (x64)". That's not to say it won't work on the later version, but you should speak with them directly about your support options.
    1 point
  12. 1 point
  13. Goodmorning I have a nakivo installation with an unique esx server as inventory. Currently i backup all vms in a qnap based on intel cpu with nakivo transporter app. I added a new qnap at the network and i'm trying to use it as second trasporter/repository. No problem adding it as transporter in nakivo's dashboard but i can't add the folder as repository cfis. The error is tha "the folder doesn't exists", so it can't create the NakivoBackup folder. Currently I have the doubt that I choosed the wrong nas : it's an Arm processor. I opened a support ticket but i'm also trying to use this f
    1 point
  14. Hi Andrea I don't know if it works with an ARM, since I don' user Qnap. Acording to the releasenotes of 10.3 you have a loss of functions if you are not using intel CPU But don't worry Just crate a SMB/CIFS Share on the Qnap and use this way: https://helpcenter.nakivo.com/display/NH/Backup+Repository+on+CIFS+Share Hope this helps Mario
    1 point
  15. Hi, I have a script which ejects the medium after the job (via "post job script") and sends e-mails to employees to replace the medium. But this is also called if there was an error during the Job (failed run). (On failure the execution of the scrip should be stopped) How can I control the script so that it is only called if the job is executed successfully? Can I somehow run a script only as a job? Then I could start this as a following job if the main-job was successful ("Run this job After successful runs"). Or is there another way to control the execution of the scrips?
    1 point
  16. Hi, at the moment I can't recreate the "bug" and don't want to try. If the error occurs again, I will contact you again. Kind regards, Jens
    1 point
  17. Hi, thank you very much for the information. It is unfortunate that it is not possible in our version But thanks anyway for the quick reply. Kind regards, Jens
    1 point
  18. Hi, I deleted the restore job because I "experimented" with the jobs But I believe that I did the restore in "Production mode". So the same vc.uuid was used in the vmx file and the backup found the wrong VM (Murphy says hello: ). I think the "Recovery mode" was the reason. Kind regards, Jens
    1 point
  19. @Official ModeratorEverything works now. Had multiple versions installed. Thank you bunch!
    1 point
  20. The product is still stuck on Ubuntu 18.04 which is five or six releases ago. Does Nakivo have any intention of upgrading to a more current version on Ubuntu?
    1 point
  21. 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.
    1 point
  22. I'm also highly interested in seeing KVM support being added, so that I could upgrade my license, adding my Proxmox workloads to the mix.
    1 point
  23. Nakivo seems to run self-backups to all repositories automatically. In my case, some of my repositories are hard drives that are ejected and stored off-site. The issue is that Nakivo automatically adds repositories as a destination for the self-backup, it would be great if it didn't do this because it generates failure notifications and the Self-Backup fails because the repositories aren't available.
    1 point
  24. Backups are now running. I'll assume this has fixed the issue for now. Thanks a bunch.
    1 point
  25. I already have this version installed. I was hoping you would provide a package with the VMware 7.0.2 support like you did for the QNAP earlier in this thread. I am experiencing errors keeping me from backing up ever since the VMware update. The VM cannot be processed. cannot find field: ftEncryptionMode (NoSuchFieldException)
    1 point
  26. Please let us know if you ran recovery in the "production" or "synthetic" recovery mode. In the "production" mode and all uuids from original VM are used for restored one, that could cause the described situation.
    1 point
×
×
  • Create New...