Official Moderator

Hello, It is possible to check the backup consistency in a few ways: 1. Run "Verify all backups" maintenance ( https://helpcenter.nakivo.com/display/NH/Running+Block-Level+Backup+Verification?src=contextnavpagetreemode ) 2. Run Flash boot action for affected VM ( https://helpcenter.nakivo.com/display/NH/Performing+Flash+VM+Boot+Recovery?src=contextnavpagetreemode ) and check by yourself if necessary files are present 3. Run File level recovery action ( https://helpcenter.nakivo.com/display/NH/File+Recovery?src=contextnavpagetreemode ) and check by yourself if necessary files are present For deeper investigation of this issue by our Support team, it would be better if you generate and send a support bundle ( https://helpcenter.nakivo.com/display/NH/Support+Bundles ) with the name of VM, that they need to check. Also provide any additional information considered to be important for this case.

As of now, physical Linux is not supported yet as it's just the first phase of physical server support with support of Windows Server only. Support of Linux OS is planned for the next releases.

There is no video on the full VM recovery, however, we have step-by-step instructions for full VM recovery with screenshots (depending on your hypervisor) in our Knowledge Base: https://helpcenter.nakivo.com/display/NH/VMware+VM+Recovery https://helpcenter.nakivo.com/display/NH/Hyper-V+VM+Recovery

Hi! We have several questions to clarify: 1. Which package is installed on location B - Full or transporter only? 2. Transporter on B has repository that in located on Synology via CIF/NFS, correct? 3. >>I tried adding the repository of location B but it only accepts local directories. This is not clear because if you added the repository as CIFS/NFS it should also work on site A. 4. >>So i tried on location B to add the NFS not on the Nakivo level but on the OS Could you please issue the "mount" command on B transporter? A point of interest is squash options of NFS. It should be "no_root_squash" or "all_squash". You may also try doing the following on B transporter: #su -s /bin/bash bhsvc #cd <mount point of NFS> Try create/remove fie or directory. Also, we would like to suggest you opening a ticket with NAKIVO support regarding this matter(send your request to support@nakivo.com).

Please use that guidance on how to detect a bottleneck: https://helpcenter.nakivo.com/display/KB/How+to+Identify+Bottleneck

You may refer to the following NAKIVO article regarding this matter https://helpcenter.nakivo.com/display/NH/File+Recovery

If you are using the Virtual Appliance (VA), go to the VA console, then go to command line and enter: cat /opt/nakivo/director/forgot_password.txt The security string will be displayed on the screen. You can copy-paste it into the web interface.

Please perform the steps from the following article https://helpcenter.nakivo.com/display/NH/AWS+EC2+Backup

NAKIVO will display inaccessible VM until that VM is still present in the job. Please edit the job, deselect inaccessible VM (from the right panel, you may have to click on x), save the job and refresh inventory.

You can keep job history and system events for 30 days, please refer to the next article for more information https://helpcenter.nakivo.com/display/NH/System+Settings

Site Recovery Job is a special job that automates execution of one or multiple Site Recovery actions. You can execute your Site Recovery Job on demand or on schedule. For more information, please take a look here https://helpcenter.nakivo.com/display/NH/Site+Recovery+Job

The appliance runs Ubuntu 18.04, 64-bit. Use the following credentials to log in to the appliance: Username: root Password: QExS-6b%3D https://helpcenter.nakivo.com/display/NH/Deploying+VMware+Virtual+Appliance#DeployingVMwareVirtualAppliance-WebInterfaceLogin

Yes, NAKIVO supports Free ESXi, but there are some limitations that can be found in the following article https://helpcenter.nakivo.com/display/KB/Free+ESXi+Backup+Limitations

VM Backup: -Keeps many recovery points -Compressed and deduped, which results in small footprint -Retains data for long periods of time -Relatively cheap -Even with technologies such as flash boot, recovery from backup is not practical with site disaster recovery VM Replication: -Required for a quick VM recovery -An exact copy of the source virtual machine -Fast recovery especially for primary site failure -Expensive to implement offsite DR facility as replication target -Can have local replicas for data store and another failure

Please check the following link for more details ( https://helpcenter.nakivo.com/display/KB/VMware+CBT+or+Hyper-V+RCT+is+Not+Supported )