This is all in regards to a single VM on the ESXi 6.5 host. All other VMs are ok.
I had attempted a recover operation, which had failed. I then shutdown all VMs and rebooted the host. I noticed this error message a day later (there was also a Replication 'failed' status, but that cleared up in another 24 hours).
I just rebooted the Replication Appliance VM, and the same message is still there.
I replicate via Veeam but anyway - it is possible that a VM is running but already corrupt. You'll find out during the next reboot. The replicator doesn't 'see' this so it will replicate corruption.
Example: bad virus scanner signatures delete dll files that are required to boot but not later since they are already loaded into memory.
Thanks for the reply.
But, I am specifically interested in a VM that refuses to start up because of some sort of issue with the VM files (I understand corrupt guest OS files will be replicated to the backup).
To try to clarify my questions:
A) The final (assumed) step (#6) was to do a 'Recover' once the backup VM had been replicated to the host. Once that's done, do I just delete the backup-to-primary replication and re-add it as the original 'primary-to-backup' replication?
B) When I stop the primary-to-backup replication (step #3), is it a 'Stop', or a 'Pause'?
Basically, as someone quiet new to ESXi and Replication services, I am hoping for simple but descriptive steps to use replication in a practical situation to recover a VM (and not leave it running on a backup host).
Basically, as someone quiet new to ESXi and Replication services, I am hoping for simple but descriptive steps to use replication in a practical situation to recover a VM (and not leave it running on a backup host).
This would depend on what application you're going to use. No steps will be helpful (or even methodologies) unless there's a specific product in mind. So are you asking specifically about vSphere Replication with vCenter or something else like Veeam?
My apologies if I was unclear. I am specifically interested in vSphere Replication with vCenter.
Download firefox and flash player and go to options > content > set lanuage to english. VDP configure page will come up in English.
Then, yes, you basically have the steps down. In vSphere Replication there is no fail back functionality. Once you bring up a replica, the replication stops at that point and you must manually reconfigure it to point back to the "source" host. Also, keep in mind that since vSphere Replication keeps the list of blocks that have been changed in memory, if the ESXi host on which your VM(s) being replicated fails, vR will require a full resync of the VM.
Thank you, that answers my question.
Since rebooting both the ESXi host and the VM in question and the vSphere Replication Appliance has had no effect, what do you think about removing and re-creating the Replication of this VM to the same backup datastore?
I guess I would want to just stop the replication and configure a new replication?
I finally took a shot and stopped the replication, and re-created it to the same location. That cleared the error, and the status is all OK now.
Hopefully, if I try to clone the VM again, I won't experience the same issue all over again.
Great, thank you!
After CBT reset, now backup of our fileserver takes from about 1 to 4 hours max, but the 1st backup (full backup) took 39 hours!
We've set a new VDP appliance for test, and we have separated another DS1513+ NAS, to check the "performance analysis" in the fresh VDP... but it's failing everytime (time exceeded).
I have upgraded 6.0 U3 to vSphere Client version 6.5.0.13000, was able to see and connect VDP 6.1.4.30 (works fine) through vSphere Web Client (Flash), but from vSphere Client (HTML5) - partial functionality interface I am not able to find and connect VDP.
looks it just available through the vSphere Web Client (Flash), HTML5 doesn't support VDP (not added ).
I was running 5.0U2 on an Asrock Z77 Extreme 4, however, the MB appears to have died.
Will I be able to just swap the motherboard with another (eg Asus P5QE, that I tested under Esxi 5.1 years ago, so might work under 5.0U2, or a new X10SRA that is on the 5.5V2 HCL, or P10S-E/4L 6.0U1 and 6.0U2 HCL) and expect everything to work without problems?
My biggest concern is my FreeNAS VM, that uses RDMs, and I am concerned that changing the MB, and/or a new install of ESXI will change the RDM mapping.
The only reason to consider using the old P5QE MB would be to check I have all the back ups I need, before a proper upgrade of the Host.
Are there any precautions I need to take before booting the host on a new MB, or starting the FreeNAS VM?
I am running into this as well.
2018-03-08T17:17:04.762Z avtar Info <5174>: - Reading /usr/local/avamar/etc/usersettings.cfg
2018-03-08T17:17:04.762Z avtar Info <5905>: Incremental flags: --flagfile=/usr/local/avamar/etc/usersettings.cfg --password=**************** --vardir=/usr/local/avamar/var --server=vdp02 --id=root --bindir=/usr/
local/avamar/bin --sequencenumber=38
2018-03-08T17:17:04.762Z avtar Error <7922>: Invalid expires input value (expires=1520529250)
2018-03-08T17:17:04.762Z avtar Error <8939>: Errors occurred preparing for backup (exitcode=152). No backup will be created.
2018-03-08T17:17:04.762Z avtar Info <6149>: Error summary: 2 errors: 7922, 8939
2018-03-08T17:17:04.762Z avtar Info <8468>: Sending wrapup message to parent
2018-03-08T17:17:04.763Z avtar Info <5314>: Command failed (2 errors, exit code 10002: invalid command line flag(s))
You should try XSIBackup, you can download it at: https://33hops.com/xsibackup-vmware-esxi-backup.html
UPDATE 2018-03-22: now XSIBackup free edition features deduplication and differential backup without any limitation. The Pro version offers post-backup data integrity certification by means of sha1 checksums and many other professional features.
We have a free version (the link above) and a commercial version called XSIBACKUP-PRO ( https://33hops.com/xsibackup-pro-vmware-esxi-backup.html )
The free version has no limitations and can backup to a datastore or to any SSH server using Rsync, by means of the Delta algorithm.
The Pro version offers advanced features, like deduplication over VMFS, instant differential backups (no checksum wait), raising events on backup end, support for Borg Backup backends, and much more.
- FREE: performs hot backups, so your VMs will always be available.
- FREE: it also performs cold backups, shutting down your VM prior to the backup and turns it on when the backup has finished.
- FREE: warm backups; shuts down the VM, takes a snapshot, switches it on and back up the guest.
- FREE: cron programmable.
- FREE: can automatically make room for your new backup in the backup device once it is full based on the full size of the device or a configurable space limit.
- FREE: it is capable of using Rsync to perform differential backups, mirrored to a second ESXI box or to a local datastore.
- FREE: can overwrite backups or create a new folder for each new backup.
- FREE: self capable, will run in the hypervisor without the need of additional hardware.
- FREE: it's totally free for personal and commercial use.
- FREE: works on the free version of the ESXi hypervisor.
- FREE: creates and uses it's own SSL key pair allowing to stablish trust relationships between different servers that will be preserved across reboots.
- FREE: super easy to install by just cutting and pasting an install script downloadable here: https://33hops.com/xsibackup-vmware-esxi-backup.html
- PRO: backup ESXi configuration.
- PRO: customize XSIBackup e-mail layout.
- PRO: control and backup 20 servers from one point.
- PRO: chain actions upon backup end, other backup jobs or external progs/ URLs.
- PRO: certify backups, compare data disks hashes upon backup completion.
- PRO: warm backups, maximum compatibility, minimum downtime.
- PRO: © OneDiff Technology, instant diff backups to DS & over IP.
- PRO: Borg Backup support, block level + compression de-duplication backend.
- PRO: © XSINAS, block-level deduplication backup device.
- PRO: © XSITools, block-level deduplication over VMFS.
You can find the man page at: http://33hops.com/xsibackup-help-man-page.html
And a lot of useful posts and how-tos at: http://33hops.com/blog-main.asp?lang=EN
Hi, you can try VMcom Backup Appliance (https://vmcom.com) instead of VDP for linux file-level restores.
It supports both xfs and ext4 and also multiple partitions on a single vdisk. At this point, it does not support LVM though. (LVM support will be added in near future.)
Cheers, Pavel
Please try running the NTP service on the ESXi server where the proxy/VDP appliance resides and then try again.
Regards,
Harish Venkatachalam
Are you using custom retention for this backup job? Like keep daily for so many monthly for so many?
If yes, then probably the keep daily value is equal to 0
Change this to a non zero value and re-run the job
# Suhas