Jump to content
NAKIVO Community Forum

Leaderboard

Popular Content

Showing content with the highest reputation on 10/13/22 in all areas

  1. We just purchased some Wasabi storage and starting a Nakivo copy job to get some of our data up in the cloud. The copy is running extremely slow, averaging about 10-15Mbps. When I manually copy files into a Wasabi bucket (with another piece of software) I can get over 30MBps (240Mbps) easily, using the exact same hardware. I know that Nakivo will create some overhead in copying from a local repository into a cloud repository, but this amount (16 times slower) is unacceptable. Is there a way to configure Nakivo to run this any faster?
    1 point
  2. > Please clarify details on how you check the speed to Wasabi manually. Which software/commands do you use? I'm using Wasabi Explorer, running it on the same Windows machine that my Nakivo Transporter runs on. Wasabi Explorer also lets you increase the number of threads in use. I cranked it up awhile ago, and now I'm getting speeds around 150 MBps (1200 Mbps) while Nakivo limps along at 20 Mbps I'll likely need to set up a test job for steps 1-3. The backup that I'm trying to copy up to Wasabi now is 12TB, and I estimate it will take 8 more days to finish.
    1 point
  3. Hi, anyone else experiencing slower VMware Backups since September Patches? We just noticed, the transfer speed drops from ~4GB/s to 1 - 1,5 GB/s Someone else noticed such drops in VMware performance?
    1 point
  4. I have recently been having issues with my S3 repository bing inaccessible, after verifying all backups i found out that this was due to some recovery points being corrupted, so obviously i attempted to bulk delete all corrupted recovery points in order to get everything running again, but the delete process just doesn't execute. next thing i wanted to try was detach and reattach the repository, but since attempting to delete the files the S3 repository has been in a constant loop of refreshing, leaving me unable to do anything to manage the repository. this process of refreshing takes much longer than usual, and once it's finished it starts anew immediately. this is related to the support ticket with the number #166925
    1 point
×
×
  • Create New...