Jump to content
NAKIVO Community Forum

Leaderboard

Popular Content

Showing content with the highest reputation since 09/18/20 in all areas

  1. Hi Nakivo Is it possible to add MFA option for the Webinterface. I have some customers, where MFA is required for the backup. Thanks Mario
    2 points
  2. Great to get 2FA for the Login Just found the option Store backups in separate files: Select this option to enable this backup repository to store data of every machine in separate backup files. Enabling this option is highly recommended to ensure higher reliability and performance. Why this is more reliable? Does this have an effect on the global dedup? And can I convert the curent backup to this option? From my point of view, the Repos are the current bottleneck of Nakivo. if there is an improvement with this, it is very welcome!
    2 points
  3. Thank you so much for your help. It worked for me using win SCP.
    2 points
  4. 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 (Paste one by one command and Press Enter): var a=Ext.ComponentQuery.query("transporterEditView")[0] a.masterPasswordContainer.show() a.connectBtn.show() you get new fields in the Browser: - Master password: - Connect Button In Master password: <ThePassworfromTheSSHCommand> (Same as used here in the bhsvc -b "<UsePassword>") Press Connect Button Then Refresh Transporter an Repository by Boris
    2 points
  5. 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 I'm turning it off to see what happens with just weekly and monthly backups. These are my settings: Retain one recovery point per day for 7 days Retain one recovery point per week for 4 weeks Retain one recovery point per month for 12 months Retain one recovery point per year for 11 years Tape Job Options: Create Full Backup: Every Saturday Tape appending: Start full backup with an empty tape** **I found that now that daily backups are turned on, Nakivo will start writing daily backups to my Full Backup tape before I get a chance to eject it. This is not desirable, but there is no options to segregate GFS tapes. Setting this to "Always start with an empty tape" would burn a tape each day, also not desirable, but I may have no choice. I would like to append all daily backups to the same tape and keep it in the library and only offsite my weekend full backups.
    2 points
  6. 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
  7. The shortest way to integrate this without going vendor specific, is adding SAML 2.0. This would allow logins based on Microsoft 365 or other MFA vendors.
    2 points
  8. Hi. I updated one of my offsite NAS units to DSM 7 and found out through support that 10.4 does not support it. Now I am left iwth having to do a physical initial seed on a DSM 6 unit or wait for certification on DSM7. They are hoping it will be done this month! Is there anywhere I can find out compatibility matrix with Synology and Nakivo? Very Frustrating.
    1 point
  9. Hi I'm setting up an new Ubuntu Server 20.04 as repo to test the "Immutable Repository" feature. I can create repos on this system without encryption, but I'm not able create encrypted repos. The error: repo-test: Cannot create the backup repository An unknown error has occurred during "repo-test" backup repository processing. I installed the following additional packages: ecryptfs-utils cryptsetup How can I get encryption working? Thanks Mario
    1 point
  10. Hello everyone, I have a Microsoft Hyper-v server 2019, and I implemented a backup of two virtual machines ( 1 domain controller 2019 and 1 exchange server 2019). I noticed that some folders are missing in the domain controller backup and only the main exchange server database is shown in the exchange server backup but there should be other databases in it, too. I noticed that by doing the recovery procedure. How can I solve the problem? Thanks.
    1 point
  11. Hi @Moderator I don't want to encrypt the partition, I like to setup the encryption for folders as written in the helpcenter: https://helpcenter.nakivo.com/display/KB/How+Backup+Repository+Encryption+Works The ecryptfs package provides encryption of folders Ubuntu When you create a Backup Repository on a Ubuntu machine, you can enable encryption for that Backup Repository. The cryptsetup approach will be used for devices and partitions. The file system of the encrypted device/partition will be transformed to ext4. At the same time, the ecryptfs approach will be used for encrypting folders. Thanks Mario
    1 point
  12. I have a fresh install of Ubuntu Server 18.04 with nothing but the following done to it before installing Nakivo "NAKIVO_Backup_Replication_v10.4.0.56979_Installer-TRIAL.sh" sudo apt update sudo apt install nfs-common sudo apt install cifs-utils sudo apt install open-iscsi sudo apt install ntfs-3g I installed Nakivo with flags " --eula-accept -f -C" since I am using NFS instead of onboard repository. You can see in 10.4 that multiple fields are missing. Where is the data storage policy ("Forever incremental" etc)? Where is the deduplication option? I don't want compression in Nakivo as my TrueNAS storage does LZ4 compression already. Even though Data Size Reduction is set to Disabled, it's still telling me that fast compression is set (even though I toggled that to Disabled, before setting Data Size Reduction to Disabled). If I experiment and turn the Data Size Reduction" to Enabled, I am then able to change compression to Disabled and have that stick, but still - deduplication remains off, and that matters greatly to me. Still no idea what my data storage policy is. I uninstalled 10.4 and installed 10.3 on the same box, and that is behaving correctly. Compare the screenshots. 10.4 is a hot mess for NFS right now and I simply cannot use it. You broke login wallpapers in 10.3, which was annoying, but this is simply horrible. Where are your testing procedures? Support bundle from 10.4 has been sent. I am running 10.3 now so you'll have to replicate in your lab, which should be easy to do.
    1 point
  13. The problem was with Check_mk 2.0-agent, MaxConnectionsPerSource was set to 3, so that's why the agent stopped responding. I'm running some scripts via mrpe to check status of jobs.
    1 point
  14. The support bundle link gives "Page Not Found". The URL has an extra ")" at the end.
    1 point
  15. 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 forum. Thanks
    1 point
  16. Hello, @Mike Spragg can you please explain how exactly the "sshd_config" file is modified? Is ist possible to make the changes remote? Maybe you can explain the necessary steps? Thank you in advance! Axel
    1 point
  17. Hello, We need to be able to encrypt the backups repositories that are stored on windows servers. Is this something that is considered for future Nakivo versions? We would like to have safe backups, even if the Nakivo console would be compromised by hackers.
    1 point
  18. Hello, Indeed, there is no client portal with authentication. So for those who would ask the question like me. The first time you have to download items, take them all. If you want an old version, you will have to ask the support. Thank you @Mario and Mr. or Ms Official Moderator.
    1 point
  19. In HotAdd mode, virtual plates from the virtual machines being supported up are naturally mounted to the intermediary, so they can be gotten to by the intermediary as neighborhood circles. The ESX have the intermediary is running on should approach all datastores for the virtual machine. In the event that the virtual machine and the intermediary are not on a similar host, all datastores should be divided among the hosts and the hosts should be inside the equivalent datacenter. In the event that SAN mode isn't accessible, HotAdd mode can accomplish near SAN mode execution. To empower gradual reinforcements of virtual circles, Changed Square Following (CBT) should be utilized for the main full reinforcement. (CBT is empowered for reinforcements of course.)
    1 point
  20. 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
  21. Same problem with NAKIVO Appliance and Transporter + Repository on SYNOLOGY Same trick wor like a charm BUT: First stage on SYNOLOGY /volume1/@appstore/NBR-Transporter# ./nkv-bhsvc stop ./bhsvc -b "<UsePassword>" Aftter these restart Service from Synology console Connect to NAKIVO Console , edit Transporter , Connect .et voila :))
    1 point
  22. Thank you ! I hit this problem pretty much straight away as soon as 10.3 came out. Unfortunately, there is a down side insofar as you are weakening what was a hardened system so hopefully fixed in 10.4 without the need to do this.
    1 point
  23. I have a question (suggestion) regarding licensing. Why don't you make an independent license server that the Directors could rely on regardless of the installation. Example: because I will have more than 800 transporters in a near future, I installed a Multi-tenant to separate eleven "Tenant". With an independent license server I could have installed several single-tenant Directors, one for each organization With this architecture I secure my Directors (today I lose the multi-tenant (crash, cyber attack, ...), I block all my backups and restore) Same, I facilitate the update (not a bigbang). sorry for my aproximative English.
    1 point
  24. ... 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
  25. 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
  26. 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
  27. 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
  28. that was done this morning with link to URL of this discussion in summary as well as the question that started this
    1 point
  29. 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
  30. 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
  31. I noticed that on Windows server, I can only run one job at a time. When I backup to tape or Wasabi, I cannot run my scheduled backups. QNAP says that Nakivo does not have this limitation when running on a Intel or AMD based QNAP NAS. I assume that on QNAP the Backup Copy jobs are running from a snapshot freeing the primary backup to be used at the same time? What other repositories allow replication or backup copy jobs while source backups are running? Synology? FreeNAS? Linux? - Ed Hammond
    1 point
  32. The difference is that VMware offers dynamic memory support for any guest OS, and Hyper-V has historically supported dynamic memory only for VMs that run Windows. However, Microsoft added dynamic memory support for Linux VMs in Windows Server 2012 R2 Hyper-V.
    1 point
  33. Hello, I think it would be great if you all could add a report feature to the product. Nakivo is a key part in my DR strategy and being able to have reports that show for example how long it took to restore backups, perform backups etc. would help when talking to business stakeholders.
    1 point
  34. 1 point
  35. Hello i had the same probleme here ! Do you have any package for QNAP QTS ? Thank in advanced !
    1 point
  36. I'm running 10.2.0.52518 and it seems to be not compatible with vmware 7.0.2 i get the error An internal error has occurred. Reason: cannot find field: statelessNvdsMigrationReady (NoSuchFieldException). When will we have a release that is compatible with vmware 7.0.2 ?
    1 point
  37. Hello, for 2 days i have been trying to add a w10 pro machine and i have errors. first it was necessary to authorize access to c $ by adding a key in the registry. But since then I have the error "An internal error has occurred. Reason: cannot install transporter, code: -1, reason: command finished successfully (WindowsDeploymentServiceException)." I tried on several workstations, laptops, VMs and I have the same problem. Nakivo full is installed on a W10 pro workstation which is on the same network. If anyone has already succeeded and has a solution ...
    1 point
  38. it's done, and it doesn't change anything, I sent an email updating # 80384 with the install.log files
    1 point
  39. Why do not try oauth 2.0 ??? It`s cheaper and much easier to use
    1 point
  40. If I have Nakivo installed and running on a vm how do i back it up? I noticed that if i try to include the nakivo vm in any existing backup jobs i run into issues.
    1 point
  41. Hello, can you consider creating some kind of MySQL DB restore functionality? I would love to have this kind of mechanism which is creating .sql file or it is restoring DB from backup to new selected DB. Thanks
    1 point
  42. I can tell you how it works manually or how it works in R1Soft / Idera backup software (basically it is the same way). I can do it here or in some ticket.
    1 point
  43. 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
    1 point
  44. I have a new vSphere 7.0U1 farm and new Nakivo server setup. I tried to backup VM on ESXI host, I got the following error message. All backup jobs got the same error. Local reseller already helped to upgrade Nakivo to 10.1.1 (build 49573 from 2020 Nov Sat at 12:11:00 PM) but the result is still same. VMware vSphere Storage API error has occurred on the "Onboard transporter" transporter.
    1 point
  45. I got an answer from Support which sparked a realization. I believe I have figured out the problem. The transporter instance size was much smaller than the target EC2 instance. I deployed a new transporter of a size that matched the target instance and kicked off the backup. It is running now and no errors so far, knock wood.
    1 point
  46. Just to follow up ... I was able to backup a test instance with a 500g attached volume successfully. But the production target server still fails. I transmitted a support bundle to Nakivo using the built in tool. Unpacking the bundle, I found in the events.log an error "NoAppropriateTransporterInAwsRegionAlarm ... There was a problem with the "SelectAndLockTransporters" action ("<hex> <name>" instance). Time spent: 0 seconds. Reason: cannot select transporters." Not sure how it would be different...
    1 point
  47. Hello, @Bubbles At the moment, NAKIVO supports only the following bare metal hypervisors: -VMware ESXi; -Microsoft Hyper-V; -Nutanix AHV; Other supported platforms may be found here: https://helpcenter.nakivo.com/display/NH/Supported+Platforms Proxmox, KVM and other hypervisors that are currently not supported are in NAKIVO logs and will be added in future releases. We are constantly working to improve our software solution and your posts help us to understand your needs better. Thank you.
    1 point
  48. Thanks. So please confirm what I am reading. Running "apt update' followed by "apt upgrade" is safe. Running "apt dist-upgrade", "apt full-upgrade, and/or "apt autoremove" is also safe? Running "do-release-upgrade" followed by associated apt commands is NOT safe. Sounds like you covered by 1st and 3rd points, but I'm still a little fuzzy about the second.
    1 point
  49. Thank you. Someone from Nakivo Support helped me already. This is what I did: to increase java memory on NAKIVO application as following : 1. Stop NAKIVO service from the AppCenter 2. Connect to Synology via SSH using "root" 3. edit nkv-dirsvc file ( mostly that file is located in /volume1/@appstore/NBR/nkv-dirsvc ) and replace: SVC_OPTIONS="-Dfile.encoding=UTF-8 -server -XX:+AggressiveOpts -XX:-OmitStackTraceInFastThrow -Xnoagent -Xss320k -Xms128m -Xmx320m" with: SVC_OPTIONS="-Dfile.encoding=UTF-8 -server -XX:+AggressiveOpts -XX:-OmitStackTraceInFastThrow -Xnoagent -Xss320k -Xms128m -Xmx640m" 4. Start NAKIVO service Thank you. Juraj.
    1 point
×
×
  • Create New...