Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 01/03/23 in all areas

  1. Could I suggest you include these instructions for manual download and installation on DSM 7 for the current and future versions on the main Updates page (with suitable caveats/warnings). The Synology approval process is clear far too slow (it can take months for an update to appear, and even then it tends to lag behind the current version), so I suspect most of us using Nakivo on synology are now updating manually (and how to do so is becoming a FAQ). Matthew
    2 points
  2. Good morning, for a VM I would like to do only one full backup weekly. Each time the job is run, the full backup must be recreated, not incremental. How can I set the job? Thank you
    1 point
  3. 1 point
  4. Trial license 14 days to go on trial 2 Repositories Add 365 link - all OK! When I go to create a backup "JOB" - all options to select a backup type are "GREYED" out. See image attached. Why?
    1 point
  5. All looks good including Inventory items - see images attached
    1 point
  6. Hello I am having the same problem. I have windows server 2012 r2 vm under vmware esxi 6.7 The vm containts two vmdk, 200gb and 400gb - both thin. The first vmdk is for the OS, and the second is for data. I use Nakivo to backup only the first vmdk (the windows os) to deduplication repository. The first vmdk contains about 100gb. There are no much changes to this disk (it's only the server OS) , but every day the backup size is 85gb obviously something here is wrong. -Roei
    1 point
  7. Nakivo is installed as appliance without any changes. Only 2 VMs are backuped each night into the onboard repository. These VMs have about 50GB and 80GB disk size, so they are not very large. After a few days I received this warning: The "NAKIVO Backup & Replication" application is about to run out of memory. How can it happen in this small installation using the default configuration? Nakivo VM has 4GB memory and "top" shows about 2GB avail memory. I can't believe that it is a problem of java heap size of director service in this small environment. Please give me an instruction to solve the problem.
    1 point
  8. Hello @Ste-, thank you for your email. We forwarded the question to the NAKIVO product development team. We will contact you as soon as we have any updates. Thank you for your patience.
    1 point
  9. is it possible to modify some configuration file, in order to extend the list of compatible S3 provider? My company provide S3 based service, we would like to be part of that list.
    1 point
  10. Is there any news about this issue? Is it possible to specify a specific endpoint in place of the Amazon region? Using fuse is not as reliable as using http S3 API.
    1 point
  11. We installed Nakivo as VM on a VMware cluster and we want to use a backup repository on the local datastore. The default "Data Size Reduction Settings" for the Onboard Repository are "Store backups in seperate files". Unfortunately this setting can't be changed. As far as I know this means, that each VM is stored in separate files without deduplication. The backup size becomes very large. How can I disable "storing in seperate files" and activate deduplication across VMs? In principle the Onboard Repository is what we need, but we need deduplication. My first idea was to delete the onboard repository and to create a new one with proper settings, but that is not possible.
    1 point
  12. Yes, of course I mean removing LV, VG and PV. Now I have done all steps to remove the old, unneeded 500GB partition. Until now everything is still working. But you should put this use case into the Nakivo documentation, because using deduplication with a local repository is a common usage of a backup tool. Especially in small installations. And it would be very usefull if deduplication is enabled by default!
    1 point
  13. OK, I expected that there would be a simple command to integrate a new repository. It should be included into Nakivo documentation. Fortunately I have good Linux knowledge, so I did it. What do I have to do to remove the old Onboard Repository which is unneeded now? I would remove it from /etc/fstab, remove logical volume, delete partition /dev/sdb and finally remove the 500GB disk from the VM. Is it enough? Or are additional steps needed to remove it properly?
    1 point
  14. What version of Ubuntu is used in the latest Nakivo provided virtual appliance?
    1 point
  15. During creating a new repository I ended with "Cannot create the backup repository. The specified location does not exist." It seems that I missed at least one step. What have I done: - Added a new virtual disk to my Nakivo VM - On the console: "Manage Nakivo services" and press F5 to refresh the list of disks. Now both disks (the default disk and my new disk) are visible. - Connected to Web GUI and "Add Backup Repository" with type "Local Folder", a new Name, Onboard Transporter and a new path to the local folder. - In the options I configured settings for deduplication. It seems that I need to configure where the new disk is mounted in the filesystem (like /etc/fstab) . But how can I do that?
    1 point
  16. i'm can't add vCenter to inventory with Nakivo. found error : An internal error has occurred. Reason: cannot find field: memoryTieringType (NoSuchFieldException). please suggest how to fix this error.
    1 point
  17. We now use another application for backing up Microsoft 365 (e-mail). What I love about that application is that it has a pst export, this can be for individual items or a whole mailbox. We found that quite useful and gives a bit more of the feeling you're in control with a recovery. I'm now evaluating the Microsoft 365 backup of Nakivo, but found it can only recover items directly to an office 365 account. Is there any plan of implementing a pst export functionality?
    1 point
  18. @Official Moderator Thank you for that, but it is not needed anymore. I send a request to support@nakivo.com with all the information to look us up in the system.
    1 point
  19. In follow up, Nakivo Support were able to assist me via a remote session and we increased the allocation of RAM. Excellent Support!
    1 point
  20. Any update on the ETA for this feature ? We are also asked to encrypt the tapes.
    1 point
  21. Since the vSphere virtual appliance won't upgrade the OS on its own what is the process to upgrade from Ubuntu 20.04.5 LTS to 22.04.1 LTS?
    1 point
  22. Hi, how can i install nakivo 10.7.2 in synology dsm 7? thank you
    1 point
  23. 1 point
  24. @Official Moderator You can just scroll up in this topic on the 22nd of August, what a colleague of you said. I already opened multiple times a ticket. Last one: #179832
    1 point
  25. I escalated to the product Team. Got the following response: "The product Team does not have any ETA for this improvement. It is under review right now.". On 22nd of August, you were 'working on it a short time ago'. Already more than a year waiting on this. In the meantime, our license is almost expired, and the new prices have increased with 14%. Maybe just change the naming of the editions to match the features and expectations: Pro -> Home Enterprise -> Business Enterprise plus -> Enterprise
    1 point
  26. Hello, @perrcla Thank you for getting back to us. 1. Install the NBR version 10.7.1 via Synology AppCenter. 2. Stop NAKIVO services: Package center -- Installed -- NAKIVO -- Action -- Stop. 3. Connect to Synology via SSH (Putty) using an admin account. 4. Get root privileges running the following command: sudo -i Enter your admin password when prompted. 5. Go to /root folder: cd /root 5. Download the newest NBR version installation script for Synology NAS, for example for x86_x64 platform: curl -o updater.sh https://d96i82q710b04.cloudfront.net/res/product/DSM7/NAKIVO_Backup_Replication_v10.7.2.69768_Updater_Synology_x86_64.sh (armv7 - https://d96i82q710b04.cloudfront.net/res/product/DSM7/NAKIVO_Backup_Replication_v10.7.2.69768_Updater_Synology_arm_v7.sh armv8 - https://d96i82q710b04.cloudfront.net/res/product/DSM7/NAKIVO_Backup_Replication_v10.7.2.69768_Updater_Synology_arm_v8.sh). 7. Run the following commands to replace the existing NBR director with the newest version: chmod +x updater.sh ./updater.sh 8. Start NAKIVO services if needed: Package center -- Installed -- NAKIVO -- Action -- Start. Thank you so much for your attention and participation. We are looking forward to hearing from you.
    1 point
  27. Hello, as the space on /root is not enough - and also you should NOT use /root for such downloads - I decided to cd into /volume1/share/temp [you will have to replace the share with a shared directory on your nas and create temp there] After that I could curl inside that directory and update nakivo to 10.7.2 with the updater.sh In that way it worked for me. Kind regards and happy new year @all Martin kamaste.it GmbH
    1 point
  28. Thank you for your post and interest in NAKIVO!
    1 point
×
×
  • Create New...