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

Search the Community

Showing results for tags 'onboard repository'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General Discussions
    • Announcements (Releases)
    • General threads
  • Deployment
    • Deployment
  • Configuration
    • Inventory
    • Transporters
    • Backup Repositories
  • Backup
    • General backup topics
    • VMware backup
    • NAKIVO Backup for Proxmox
    • Microsoft Office 365 Backup
    • Hyper-V Backup
    • AWS EC2 Backup
    • Backup Copy
    • Nutanix AHV Backup
    • Physical Backup
  • Replication
    • VMware Replication
    • Hyper-V Replication
    • AWS EC2 Replication
    • General replication topics
  • Recovery
    • File Recovery
    • Object Recovery
    • Full VM Recovery
    • Site Recovery
  • Integration
    • Integration
  • Automation
    • Automation
  • Multi-tenant Mode
    • Multi-tenant Mode

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 1 result

  1. 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...