Jump to content
NAKIVO Community Forum


  • Posts

  • Joined

  • Last visited

  • Days Won


rimbalza last won the day on August 31 2023

rimbalza had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

rimbalza's Achievements

Data Defender Cadet

Data Defender Cadet (2/14)

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

Recent Badges



  1. Hi, I'm using 10.8 on Linux to backup VMs from HyperV. I have several VMs with a lot of RAM like 32 or 48 Gb. When I test my restores I cannot use as a destination an host with less ram than the original VM. For example I want to restore a VM that has 48 gb of RAM on a host that has 32 GB. The process does not even start, it blocks the configuration procedure saying the host needs more RAM. I find no way to say to resize the RAM or continue anyway. This is an horrible design decision for at least a couple of reasons: - In my case I just restore the VMs and do NOT power them on, there's an option for that. Still Nakivo says I cannot restore. - In an emergency this requires you to have a full set of working hosts with at least the same RAM as you had before, and this again is an awful decision that hinders the ability to use Nakivo for real world recovery scenarios. I am in charge of the restore and if I decide to restore to an host with less RAM than the original one it should be my problem. I understand a warning from Nakivo, I cannot understand why blocking the restore. On HyperV you can create any number of VMs with any amount of RAM, then you decide which one to start or to resize. Reducing the restore options for no pratical benefit and imposing artificial limits is just silly. Is there a way to force Nakivo to continue the restore? Thanks
  2. I miss what information you can get from a support bundle that is not in my post above. If this is some sort of "if you're not a paying customer we don't even consider your suggestion" I think you're doing it very very wrong. And yes, I'm a paying customer.
  3. I have a S3 bucket used as a repo. I see that everyday the backups add new data. I don't know if older files on that bucket are used (some or all, I don't know) each time new ones are added, but if they are not it is possible to creare a rule that moves older files to a different storage tier, for example STANDARD_IA. This is a tier where you pay a lot less more for keeping files that you do not access on a regular basis. In this way you can obtain big savings on the AWS bill. Also using other providers can be useful since it is API compatible with S3 but prices are way lower than AWS. The global aim is to keep offsite backup as cheap as possible, when you start having lots of TB to keep.
  4. Hi, I would like to know if it is possible to change the storage class of S3 repos. For example transitioning to Infrequent access files that are created after one week or something like that. Thank you
  5. Hi, I have two questions that are easily answered with any backup software but I cannot find how to do it with Nakivo: 1. How to backup a remote file share: \\myserver\abc. Every bit of documentation and thread refers on how to put e repository on a SMB share, but I need to backup the content of that share. I cannot install anything on the host of that share, jut need to grab the files using user/password as any backup software does. I have a transporter in the same network as the share. 1.1 If that share is instead on a NAS like Synology where you can actually install the Transporter, how do you use it to backup that share that is local to the transporter? I know those are dumb and easy questions, but seems impossible to do with Nakivo... Thanks
  • Create New...