Jump to content
NAKIVO Community Forum

Official Moderator

Moderators
  • Posts

    398
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by Official Moderator

  1. Yes, that algorithm of using one storage with two transporters is possible. But please pay attention that if second transporter will try to attach the repository, it could lead to the repository corruption.
  2. Repository could be processed only by one transporter at the same time. However, few repositories could be processed by one transporter, we recommend to attach not more than 5 repositories to one transporter.
  3. The latest build that is present on our web site supports ESXi 6.7u3, please update NAKIVO Backup&Replication - https://www.nakivo.com/resources/download/update
  4. Yes, 9.1 is still in beta. You need to install NAKIVO 9.1 in order to try tape. Please check the following link to download necessary installer - https://www.nakivo.com/resources/releases/9.1-beta/ Please check the following link for full beta requirements https://beta-helpcenter.nakivo.com/display/NH/Feature+Requirements#FeatureRequirements-NativeTapeSupport https://beta-helpcenter.nakivo.com/display/NH/Tape Please note that beta can be used only for testing purposes.
  5. Please update your NAKIVO instance with our latest GA version available on website: https://www.nakivo.com/resources/download/update/ You can use the following article as a guidance https://helpcenter.nakivo.com/display/NH/Updating+NAKIVO+Backup+and+Replication
  6. Hello Matt! Could you please clarify what NAKIVO B&R version do you use? The tape support is added in v9.1.
  7. Hello! This is NAKIVO Backup&Replication forum. Could you please clarify your question in more details so we can provide you with a proper answer?
  8. Hello Mario! The reasons for low speed can be different and we cannot say for sure why it is so without investigating the logs that were collected by profilers. That's why performing the steps from the "bottleneck" link ( https://helpcenter.nakivo.com/display/KB/How+to+Identify+Bottleneck ) is the best solution for this issue.
  9. With the new version of the solution, you can copy your backups to tape, back up your Linux Servers, and perform instant verification of your backups for additional reliability. Learn more about NAKIVO Backup & Replication v9.1 Beta > https://www.nakivo.com/blog/nakivo-backup-replication-v9-1-beta/# Download NAKIVO Backup & Replication v9.1 Beta, sign up for our Beta Program, and receive an Amazon eGift Card for your efforts!
  10. We are sorry but NAKIVO Support doesn't have an access to Cloudways so we cannot check the platform.
  11. Usually, the customer adds the AWS access and secret access keys to the NAKIVO inventory that allows accessing the AWS server instance. We are not sure if Cloudways provides the access to API. So in your case, we can suggest backing up your web server as Physical Linux server. It will be supported in v9.1. The Windows physical server is supported starting from v9.0.
  12. 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.
  13. 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.
  14. 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
  15. 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).
  16. Please use that guidance on how to detect a bottleneck: https://helpcenter.nakivo.com/display/KB/How+to+Identify+Bottleneck
  17. You may refer to the following NAKIVO article regarding this matter https://helpcenter.nakivo.com/display/NH/File+Recovery
  18. 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.
  19. Please perform the steps from the following article https://helpcenter.nakivo.com/display/NH/AWS+EC2+Backup
  20. 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.
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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
×
×
  • Create New...