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

Recommended Posts

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.

Edited by User
  • Like 1
Link to comment
Share on other sites

1 hour ago, User said:

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.

Hello, @User, thank you for your patience. Option "Store backups in seperate files" can be set only during repository creation.

So to use deduplication please create a new repository without option "Store backups in seperate files" and use this repository as a target for the backup job.

When all jobs will be reconfigured to use the new repository, it will be possible to remove old repository from inventory and disk. I look forward to hearing from you.

Best regards.

Link to comment
Share on other sites

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?

  • Like 1
Link to comment
Share on other sites

16 hours ago, User said:

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?

Hello, @User, thank you for your post. It can be helpful to other members of our community.

Please use the following Ubuntu article to mount a new disk: https://help.ubuntu.com/community/InstallingANewHardDrive

We look forward to hearing from you.

Link to comment
Share on other sites

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?

 

  • Like 1
Link to comment
Share on other sites

1 hour ago, User said:

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?

 

@User, thank you for the update.

You need to remove LVM as well:

lvremove LVNAME

vgremove VGNAME

pvremove DISKNAME

We are looking forward to hearing from you 👍

Link to comment
Share on other sites

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!

  • Like 1
Link to comment
Share on other sites

3 hours ago, User said:

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!

@User Thank you for your post. I have sent all your suggestions to be taken into consideration, but the best way would be to generate and send a support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles) to support@nakivo.com so our Technical Support team can investigate it and forward your feature request to our Product Development team for possible future implementation.

Link to comment
Share on other sites

On 1/13/2023 at 6:44 PM, User said:

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!

 
 
Information about deduplication can be already found in our help center:
 
Please let us know if any other tech assistance is needed or the ticket can be closed. Thank you for your ideas 👍
 
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...