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

Leaderboard

Popular Content

Showing content with the highest reputation on 02/27/20 in all areas

  1. Hi on a ESXi server I had troubles with the snapshot of one VM (also when I do snapshots from the Vmware interfac, so not an Nakivo issue) Since I don't have the possibility to take the server offline, I removed the VM from the backup Job but I left the data on the repository. Then I added the VM directly as "physical server" to my inventory and created a new backup jop to the same repo. Bevor I started the new Job, I had 1.03 TB free space, the VM has a disk size of 200 GB and about 150 GB used. After the new Backup I had 900 GB of free space (100 GB used by new backup). According to your website you have "Global deduplication for economical storage space utilization" in your product. So why does a second backup of the same VM take this much space? I just use a diffrent way to backup the same data... regards Mario
    1 point
  2. 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
  3. What sort of transfer speed are others getting on backup copy jobs across WAN links? I'm setting up the repositories as FAST compression and Network Acceleration enabled and I'm getting between 3 MB/s and at best 15 MBps. The latter is with the source on a 50/50 leased line and the target on a 200/200 FTTP.
    1 point
  4. Yes, I do the full install (mostly transporter only since I have a multi-tenatn setup) and attacht the Storage from the nas as "Remote CIFS share".
    1 point
  5. So if I understand this right, you're installing the full Nakivo Windows installation on the Hyper-V server and then backing up to the NAS as a mapped drive?
    1 point
  6. Hi Simon I agree with official Moderator, it also depends on the CPU power of the included devices. Are you sending from a Server or Nas to a Server or Nas? At the beginnign I was using the Transporter on the Synology Nas, but this was a bottleneck. Now I use whenever the HpyerV/ESX as Transporter and att the storage over SMB. This has increased the processing speed. Mario
    1 point
  7. 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
  8. Hello! It could be that the bottleneck is not WAN connection speed. Please check the speed of read from source repository and speed of write to the target one. In case there is no cause, generate a new support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles) and send it to us.
    1 point
  9. Attempting to add an offsite copy onto another QNAP NAS. The RTRR transfer is very quick, however Nakivo sees the results on the receiving end as "corrupted"
    1 point
  10. Hello! We suggest you run Self-healing and Verify all backups for source and target repository. After that, generate a new support bundle (https://helpcenter.nakivo.com/display/NH/Support+Bundles) and send it to us for further investigation.
    1 point
×
×
  • Create New...