Jump to content
NAKIVO Community Forum

Leaderboard

Popular Content

Showing content with the highest reputation since 08/19/19 in Posts

  1. Hi. When is it planned Vmware 7 update 3 support?
    2 points
  2. 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
  3. @Bedders, Please try replacing "q" with "-q": zip -q -d log4j-core*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class Let me know if it works for you!
    2 points
  4. Hi, @JurajZ and @Bedders! NAKIVO Backup & Replication is using the Apache Log4j library, which is part of Apache Logging Services. You can manually fix the CVE-2021-44228 vulnerability by removing JndiLookup.class located in libs\log4j-core-2.2.jar. Note: If the libs folder contains log4j-core-fixed-2.2.jar instead of log4j-core-2.2.jar, it means that the issue was already fixed for your version of NAKIVO Backup & Replication. For Linux: Go to the libs folder located inside NAKIVO Backup & Replication installation folder. To remove JndiLookup.class from the jar file run the following command: zip -q -d log4j-core*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class For Windows: Ensure you have 7z tool installed. Go to the libs folder located inside NAKIVO Backup & Replication installation folder. Use 7z to open the log4j-core-2.2.jar and remove JndiLookup.class from the jar file. Restart NAKIVO Backup & Replication. For NAS devices: If you are using a NAS, open an SSH connection to your device and locate NAKIVO Backup & Replication installation folder here: For ASUSTOR NAS: /usr/local/AppCentral/NBR For FreeNAS/TrueNAS (inside the jail): /usr/local/nakivo/director For NETGEAR NAS: /apps/nbr For QNAP NAS: /share/CACHEDEV1_DATA/.qpkg/NBR For Raspberry PI: /opt/nakivo/director For Synology NAS: /volume1/@appstore/NBR For Western Digital NAS: /mnt/HD/HD_a2/Nas_Prog/NBR Note: Refer to the NAS vendor documentation to learn how to open an SSH connection to your NAS device. IMPORTANT: CVE-2021-44228 is a severe vulnerability. We strongly advise you to apply the manual fix as soon as you can. This is the best way to avoid the risks of security breaches. Please contact customer support if you require custom build of NAKIVO Backup & Replication that has the fix.
    2 points
  5. Hi, @SALEEL! I am very sorry that we put you in such a position. The latest improvements in DSM7 were unexpected for everyone. And it makes us feel very sad that we can't provide you with our best service as usual. Our team was doing everything to accelerate the process. However, at this point, there is nothing we can do. I understand your disappointment, and I apologize for all the inconvenience it has caused you. One of our main values is customers satisfaction. That's why this situation is frustrating. If only it depended on us! At the moment I can only offer you the following options: 1. You can temporarily install NAKIVO Backup & Replication on some other host and use the NAS-based repository as a CIFS/NFS share. When DSM7 is officially supported, then it will be possible to install NAKIVO on NAS again. 2. Workaround for DSM 7: - Deploying a new NAKIVO installation somewhere else as Virtual Appliance (VA) or installing on a supported VM, Physical or NAS; - Share the repository folder on the Synology NAS with DSM7 as NFS / CIFS (SMB) share; - Add this repository as existing to the new NAKIVO installation; - Restore the configuration of old NAKIVO installation from Self-backup from the original repository. For now, we are working closely with Synology to prepare the release, and we are almost at the final stage. However, we expect that we will need a few more weeks till the final release. Again, I am very sorry for all the convenience!
    2 points
  6. 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
  7. Thank you so much for your help. It worked for me using win SCP.
    2 points
  8. 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
  9. 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
  10. 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
  11. 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
  12. Could you please do a video for Nakivo B&R to Microsoft Azure ?
    2 points
  13. 2 points
  14. It is something that i may be interested in but i would like to see a "how to" video on the process on your youtube. I saw that you have a "how to" video on amazon ec2 backups (which is old now by the way)
    2 points
  15. 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.
    2 points
  16. Hello, thanks for support, it works. Regards Francesco
    2 points
  17. Our team is excited to announce the official release of NAKIVO Backup & Replication v9.1! The most anticipated features are finally available: Backup to Tape, Linux Server Backup, Instant Verification and Windows Workstation Backup. The fully-functional Free Trial version is here https://www.nakivo.com/resources/releases/v9.1/
    2 points
  18. NAKIVO Backup & Replication v9.0 allows you to perform an incremental, application-aware backup of Windows Servers. With our solution, you can instantly recover files as well as application objects! Download our full-featured free trial to try out NAKIVO Backup & Replication for yourself: https://www.nakivo.com/resources/releases/v9.0/
    2 points
  19. Hi, I disabled the auto refresh of the repositories but it did not make any change to the usage. After some digging it looks like the transporter ( or pgsql ) is repeatedly trying to determine the used and free space in the repository. looking at all_pg_sql.log, it keeps logging eventl like this: I suspect that the "Get used space" is the culprit where it is walking the directory structure and adding up the size of all the files in the repo (which contains ~3.3M files in this case). It appears to be triggered at tenant startup (or repo mount) and then 30 minutes after the previous iteration completes. I have also tried switching off "system.repository.refresh.backup.size.calculation" under expert settings but "Get used space" still runs.
    1 point
  20. Hi, @Garry.web! As you can imagine, the functionality is similar. The choice depends more on your environment. However, you can consider the following aspects: Features Administration Security Support Pricing and editions We have a blog post on this. It can help you compare both options https://www.nakivo.com/blog/microsoft-365-vs-google-workspace-a-full-comparison/ If I can help you with anything else, please get in touch with me.
    1 point
  21. Hi! @eric_76 @mark007, I wouldn't recommend using snapshots as a backup method for your AWS EC2 instances as it has several limitations, such as: High security risks. If your cloud credentials leak, everything including EC2 instances, volumes and snapshots can be deleted within seconds, resulting in complete data loss and no way to recover it. Very basic retention policy for storing data. You can either keep a long chain of snapshots and overpay for storage or keep a short chain of snapshots and hope the older data won’t be needed. Another option is to spend time on manual snapshot administration. All of the choices aren't efficient. You can't perform granular recovery. EBS volume snapshots are exactly what they sound like: just snapshots. All you can do with a snapshot is restore it to an EBS volume. This means that you cannot perform any kind of granular recovery from the snapshots. AWS snapshots are only crash-consistent. A crash-consistent state is good for file servers, but not for applications and databases, which store portions of data in memory and have incomplete I/O operations at the time a snapshot is made. AWS snapshots store all data without using any data reduction techniques. Therefore, you spend much more money on your storage. For security reasons and budget savings (up to 4x times), I recommend you use a third-party solution. You can check NAKIVO's offer for your Amazon EC2 backup https://www.nakivo.com/aws-ec2-instance-backup/ Let me know if you have more questions.
    1 point
  22. @darkhorse Hi! We always used Microsoft 365 plans because they have a lot of functionality. Even the cheapest options offer so many different services and apps, while the pricing is much lower than getting it separately. If you are on the budget, check the most affordable plan that includes Exchange Online.
    1 point
  23. So I am looking to update my VSphere cluster to 7.0.3.00100 and currently run Nakivo 10.4.0 and the Synology NAS is on DSM 6.2.4-25556 Update 2 and will NOT be upgraded to 7.0.1 because it does not support DSM 7. Do I just need to update to 10.4.1 to have this work fine? Or do I need 10.5 Again I am not on DSM for this particular unit.
    1 point
  24. Solved this problem by successfully downgrding DSM 7 to DSM 6.2 using the following procedure based on infos from: https://emby.media/community/index.php?/topic/89848-tutorialdowngrade-from-dsm-70-to-dsm-623/ 1. Ensure you have a telnet client available on your PC 2. In DSM 7.0, enable Telnet and SSH access 3. Using telnet, connect to your Synology NAS from your PC: (x.x.x.x is the IP address of your NAS) telnet to your NAS x.x.x.x 4. Run the following command on your NAS: sudo -i vi /etc.defaults/VERSION 5. Replace the entire contents of that file with the following: majorversion="6" minorversion="2" productversion="6.2.3" buildphase="GM" buildnumber="25426" smallfixnumber="0" builddate="2020/07/01" buildtime="06:24:39" 6. Save the file (:qw)and reboot your NAS 7. Use the Synology Assistant or any IP-Scanner to get the IP of your NAS (has changed back to DHCP) 8. Install DSM 6.2.3 using the .pat file downloaded from the Synology download center. The upgrade will start but then quickly show an error stating you are unable to downgrade and must install a version of DSM7. Don't worry, because at this point, Telnet will be available and you will be able to connect to your NAS. Synology Archive Download Site - Index of /download/Os/DSM/6.2.3-25426 9. Telnet to your NAS like in step 3, but instead of using your account credentials from before, use the following: username: root password: 101-0101 10. Repeat steps 4 and 5, replacing the VERSION file with the new contents (no sudo as you are root now). 11. Install 6.2.3 again. Your NAS should successfully downgrade to 6.2.3. I haven't verified that this will retain your data on your disks 12. Now you may upgrade to the latest DSM 6.2.x from the NAS GUI. 13. If your NAS had a static IP, you have to reconfigur your network settings as the downgrade changed back to DHCP.
    1 point
  25. Thanks for the info. I'll wait for 10.5 before upgrading
    1 point
  26. Hi guys, since a few week I cannot backup my shared mail boxex from 365 because an error "mailbox not licenced". How can I solve? I don't want to buy 365 licence for the shared mailbox. Thanks.
    1 point
  27. Hello everyone. I had the same issue on a virtual applience. Boris solution worked for me as well. 1. Connect to the Transporter via SSH (for instance with Putty) 2. cd /opt/nakivo/transporter 3. ./bhsvc stop ./bhsvc -b "<UsePassword>" (creates a masterpassword) ./bhsvc start 4. Go to the Nakivo configuration > Transporter > edit > enter the masterpassword and connect > accept the certificate 5. Fixed and working again. Cheers
    1 point
  28. Is there any way to get on a notification list, for when the updated product is released?
    1 point
  29. Hi Team, I am new for this tool, Need your help to make RestAPI Calls. To add the new server in backup jobs, how to remove it. All I want to make the automation of all the manual tasks. Thanks Sumit
    1 point
  30. I use NBR to backup (amongst others) a workstation (Windows) - the workstation has one local drive c:, one iScSI LUN added as remote drive and one remote drive as mounted SMB share. The remote drives are always accessible. I only want to backup the local drive C:. For reasons I do not understand NBR keeps readding sometimes the iSCSI remote drive to the backup although I excluded it previously. Support was very helpful and suggested to reduce or disable auto refresh of the inventory to solve this issue. I disabled auto refresh and so far it works. However, I would like to understand what is happening and maybe some of you have solved this issue in a different way? Certainly something happens behind the scenes which makes NBR detecting the same remote drive as new? Are there any drawbacks to disabling auto refresh for inventory, transporters and repos? Online documentation was not helpful in this regard and your experience would be greatly appreciated. Many thanks, Hannes
    1 point
  31. hello everyone I've enable ssh and shell in my server, but if i try to add inventory, nakivo tell me that ssh is not enable. how can i solve this problem? Thanks
    1 point
  32. @Boris Works like a charm!
    1 point
  33. Problem ix fixed via remote connection from the great support Team... thx for the fast fix
    1 point
  34. Pls update you page https://www.nakivo.com/vmware-backup/ on this - 7u1.
    1 point
  35. 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
  36. When it comes to IT planning and budgeting, you want to make sure you are getting the best return on your investment. Taking a look at Hyper-V versus VMware, each have their strengths and potential considerations. Although the two hypervisors have similar features, capabilities are somewhat different.
    1 point
  37. Same here, the performance of backup up to tape is less than stellar. Did support find a resolution?
    1 point
  38. 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
  39. The appliance is already deployed and backup several VMs. Now I want to add a linux server (debian) but installer fail when installing transporter.
    1 point
  40. Any update on the NAS version beta release dates? Thank you!!
    1 point
  41. May I know the release date for physical server restore? It is getting risky with physical server backup. But do not have a way to do full server restore to physical server.
    1 point
  42. Hello. We are running Nakivo from Synology and lately we have been getting a message to allocate more RAM. System · 17 Apr at 18:00 (UTC +02:00) Application is about to run out of memory Allocate more memory to the application. https://www.nakivo.com/helpcenter9.1/display/KB/How+to+Allocate+More+RAM+to+NAKIVO+Director+Service Could someone please walk me through this? Thank you, Juraj.
    1 point
  43. WHERE DO I GET NAKIVO V9.3 APK FOR ASUSTOR NAS?
    1 point
  44. During backup (it does not matter VM or physical) all data is divided for blocks and stored in the repository. In case some blocks appear to be similar, deduplication works and only one block is saved in the repository. It seems that in this case saved data from VMDK file and directly from VM disk has different layout (contains some additional service information or shift for example). In this case saved blocks are different and will not be deduplicated.
    1 point
  45. Hi, When you say the speed of 'read' and 'write' what do you mean? These are Synology units and the local backup to the drives gets about 130 MB/s What is odd is that the speed in the 'speedometer' varies so much. Can you explain what this is showing and whether you'd expect it to fluctuate? Here the speed is down at Zero with the job still running, but a few moments ago it was at 40 MB/s - is that right?
    1 point
  46. I also would like to test tape. is it possible?
    1 point
×
×
  • Create New...