Jump to content
NAKIVO Community Forum

Leaderboard

Popular Content

Showing content with the highest reputation since 05/12/21 in Posts

  1. Here is how to fix it... for QNAP Login to QNAP via SSH admin cd /share/CACHEDEV1_DATA/.qpkg/NBR/transporter # ./nkv-bhsvc stop Stopping NAKIVO Backup & Replication Transporter service: [/share/CACHEDEV1_DATA/.qpkg/NBR/transporter] # ./bhsvc -b "<UsePassword>" [/share/CACHEDEV1_DATA/.qpkg/NBR/transporter] # ./nkv-bhsvc start Starting NAKIVO Backup & Replication Transporter service: Use Crome Browser https://<qnapip>:4443 Go to Settings / Transporters / Onboard transporter / Edit Press F12 -> go to Console and type following JavaScript codes (Pa
    2 points
  2. Anyone else have problems with Grand-Father-Son (GFS) retention scheme not working as expected? Daily backups work correctly and the retention is correct, but instead of getting weekly and Monthly backups, all my Full backups are set to yearly week after week at both my sites where I have tape libraries. (They expire 11 years from now) I opened a ticket, but they were not able to tell me anything and claimed that everything was working fine. At the time I was not doing daily backups, so I turned that on and they work, but they didn't affect my problem with yearly backups, so for now
    2 points
  3. @Boris Works like a charm!
    1 point
  4. Dear all, I have a problem when trying to install NAKIVO_Backup_Replication_v10.3.0.55051_Installer-FREE.sh under Ubuntu 20.04. I know that it isn't fully supported at the moment but the problem is at a very early step of the installation - I can't aeven see the EULA, it stops before this step. I tried with ./NAKIVO_Backup_Replication_v10.3.0.55051_Installer-FREE.sh as well as sudo ./NAKIVO_Backup_Replication_v10.3.0.55051_Installer-FREE.sh as well as sudo su and run ./NAKIVO_Backup_Replication_v10.3.0.55051_Installer-FREE.sh after that. Everytime it's the sam
    1 point
  5. Dear Moderator, as stated above - it worked for me. I just moved the installer from root (/) to /home and there I could start the installer without problems. Thanks a lot.
    1 point
  6. Hello all, I have a problem, is it possible to make a backup of a physical server with Hyper-V installed? When i install transporter Microsoft Hyper-V host i see all virtual machines and i can make backup, but I can't back up the physical machine. So i try add Physical machine(s) but i have error because i installed transporter earlier.
    1 point
  7. ... found the problem. I tried the script from /tmp as well as / but both didn't work. After moving to /home/... it worked.
    1 point
  8. I've got the following link from support: https://maglar.box.com/shared/static/ebzm01v0080ibtvdh2ubc11s7ops58wa.sh This is a newer build, and it should fix the problems. Since I was able to fix the problems with reinstall, I won't upgrade. But maybe some else can minimize his trouble. Mario
    1 point
  9. Hi Boris Thank you for this trick I did a reinstall of all the needet stuff, it took the complete day but now it's working again. (Multi tenant setup)
    1 point
  10. Try This https://forum.nakivo.com/index.php?/topic/5883-103-issues/&do=findComment&comment=6743
    1 point
  11. Well, something is strange. At version 12.2 all system are working correct, now after the update of today i get the follwoing error: Certificate of this transporter has expired on 27 Dec 2020 at 16:31 (UTC +01:00). Replace the certificate to continue using this transporter Why was a certificate workting till today, when it expired 6 month ago? @Official Moderator can you share the information on the forum so that everyone can benefit?
    1 point
  12. I'm doing the update right now. I have the same error and requested support for this. Conclusion: if you can wait with the upgrade, then wait....
    1 point
  13. Hello, i drop the old 'onboard transporter' and create an new one. That work for me.
    1 point
  14. @Official Moderator just messaged; I had not seen your response here requesting that information
    1 point
  15. Hello everybody, i have a problem with the backup of vm´s between an esxi server and Nakivo. The following notification appears: Cannot delete temporary snapshot of the "X" VM The "Temporary snapshot aa1fb513-816a-4675-8e07-6857c4f88905" snapshot created for backup purposes has taken too long to delete. Make sure it was removed or delete the snapshot manually. We use a ESXi 6 server. Nakivo is backing up four ubuntu vm´s. Three of the vm´s has 16 GB, one 20 GB. The vm with the problem has 16 GB. The three other vm´s need 35 seconds to a minute to be backuped,
    1 point
  16. Enabling screenshot verification returns a black screen no matter what RTO and Screenshot settings I use. Nakivo considers the job successful and discards the VM before the login screen appears. Support have not been able to help so far. Any one else experiencing this issue? Any top tips?
    1 point
  17. Hello, @Mr.Ed! I am very sorry to hear that you didn't resolve your issue with the Support Team. Please continue the discussion in the opened ticket until your problem is fixed. Let me know when you find a solution for your case. As for appending all daily backups to the same tape and keeping it in the library while storing offsite your weekend full backups only, unfortunately, this feature isn't currently implemented. However, the feature request will be submitted to the Product Team.
    1 point
  18. Problem ix fixed via remote connection from the great support Team... thx for the fast fix
    1 point
  19. @Official Moderator it has been a week with no response from support. Assistance is requested.
    1 point
  20. Seeing identical issues, tried a new 10.3 ova and it has problems with generic transporter errors that are useless for troubleshooting.
    1 point
  21. Good day. When is it planned Vmware 7 update 2 support?
    1 point
  22. Pls update you page https://www.nakivo.com/vmware-backup/ on this - 7u1.
    1 point
  23. the support has already answered me. in fact, nakivo does not duplicate to wasabi. the solution would be to make a local backup with deduplication + 1 backup copy job
    1 point
  24. Hello, at a customer there is another VM backup software that is still running. the logs say "Time: Sat, 08 May 2021 23:17 Successful Backed up 1124 GB in 2h 28m. (Data Transferred: 4.14 GB 99% Savings). " with nakivo, backing up the same VM says : "Status:Successful Started:Sun, 09 May at 10:18 (UTC +02:00) Finished:Mon, 10 May at 11:39 (UTC +02:00) Data & speed:70,8 GB at 6,77 Mbit/s" how can we explain that nakivo makes a differential backup of 70GB while the other software makes one of 4GB? This is the 3rd backup, the first was 470GB and
    1 point
  25. Hello, In current version 10.3 is feature called "direct connect", which doesn't need VPN, but just for VMWare. Direct connect for physical servers will be available in 10.6. There is no official release date of it. It's been said during today's webinar. So we're still looking forward. Regards, Jaroslav
    1 point
  26. @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
  27. that was done this morning with link to URL of this discussion in summary as well as the question that started this
    1 point
  28. 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
  29. I have the same Problem after Update Nakivo on QNAP to v10.3 (from 10.2) the Onboard Transporter shows Error I do the same like for Synology except the changed Path cd /share/CACHEDEV1_DATA/.qpkg/NBR/transporter After this a new certificate.pem is created, but now the transporter and the repository are inassesibel, and refresh will not work The "Onboard repository" backup repository is inaccessible The "Onboard transporter" transporter assigned to the "Onboard repository" backup repository is inaccessible. Make sure the transporter is availabl
    0 points
  30. Hi, @Jason! If you have a "CERTIFICATE_EXPIRED" for transporter after update to v10.3 please do the following: - ssh to your Synology where Nakivo Instance is installed. - cd /volume1/@appstore/NBR/transporter. - Stop Nakivo Services on Synology. Check how to do it here https://helpcenter.nakivo.com/display/KB/Starting+and+Stopping+Product+Services - mv certificate.pem certificate.pem_orig. - Start Nakivo services. - refresh transporter (connect/accept the certificate). The detailed guide is here https://helpcenter.nakivo.com/display/NH/Refreshing+Transporte
    -1 points
  31. Hello, @Boris! Most likely, our Support Team has to establish a remote session to resolve your issue. Please send a support bundle so that you could get personalized help from our specialists. Here you can check how to generate a support bundle https://helpcenter.nakivo.com/display/NH/Support+Bundles#SupportBundles-CreatingSupportBundles If you have any doubts, don't hesitate to contact me!
    -1 points
×
×
  • Create New...