Jump to content
ON-DEMAND Webinar: The Ultimate Guide to VM Backup and Recovery ×
NAKIVO Community Forum

User

Members
  • Posts

    5
  • Joined

  • Last visited

  • Days Won

    3

User last won the day on January 24 2023

User had the most liked content!

User's Achievements

Data Defender Cadet

Data Defender Cadet (2/14)

  • Security Champion of the Month
  • Year of Data Security Rare
  • Securely Done Week One
  • First Post of the Backup Hero
  • Secure Conversation Starter

Recent Badges

5

Reputation

  1. 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.
  2. 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!
  3. 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?
  4. 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?
  5. 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.
×
×
  • Create New...