Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
- Index
- » Search
- » Posts by eyes
#1 General matters » XSI-PRO 11.2.15 Error: The Authenticity of Host Can't be established » 2019-12-29 22:22:58
- eyes
- Replies: 1
Problem:
Backups fail. Keys cannot be exchanged. If anyone has observed this behavior and can provide a work-a-around that would be appreciated.
+++++++++++++++++++++++++++++++++++++++++++++
Source server EXSI 6.7U3. New install of 11.2.15 code. License key added from website to root directory.
+++++++++++++++++++++++++++++++++++++++++++++
Step #1
From GUI: Key Exchange for Transparent communications fails with message:
The Authenticity of Host (xxxxx) can't be established. RSA Key Fingerprint is SHAxxxxxxxxxx. Are you sure you want to continue connecting (yes/no)? yes
Password:
sed: unmantched '/'
Cannot find an authorized_key file at xxxxx
Tip: you might need to install additional Openssl components, or just create the file for your OS, it usually requires 0600 permissions.
Killed
Observation: No text added to /etc/ssh/keys-root/authorized_key
Step #2
Executed link-srv=1.2.3.4=22
This command succeeds with text added to /etc/ssh/keys-root/authorized_key
Step: #3
Executed backup
App requested password ... very odd.
Step #4:
Backup fails:
stty: standard input
c
[H[J2019-12-29T21:50:33| ###############################################################################
2019-12-29T21:50:33| XSIBACKUP-PRO 11.2.15: new execution request
2019-12-29T21:50:33| ###############################################################################
2019-12-29T21:50:33|
2019-12-29T21:50:33| NOTICE: (c) XSIBackup kills any user launched jobs, make sure you don't overlap manual jobs
XSIBackup PID: 12760815 EBNY-2015
Sun, 29 Dec 2019 21:50:33 +0000 IPv4: 192.168.1.48/255.255.255.0
VMware ESXi 6.0.0 build-2494585 (c) Rsync 3.1.0 as opt. dependency
Backup Id: test Intel(R) Xeon(R) CPU E5-2623 v3 @ 3.00GHz
2019-12-29T21:50:34| Alert: crontab is not installed for user root
2019-12-29T21:50:35| ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
2019-12-29T21:50:35| Backup user is: root
2019-12-29T21:50:35| Backup program is: xsidiff
2019-12-29T21:50:37| Remote OpenSSH version is: 7.9
2019-12-29T21:50:37| Negotiated Cipher (server->client): aes128-ctr
2019-12-29T21:50:37| Negotiated Cipher (client->server): aes128-ctr
2019-12-29T21:50:37| Service OpenSSH ready at server 192.168.1.70:22
2019-12-29T21:50:37| Remote ESXi version is Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:50:37| Info: XSIBACKUP-PRO will now try to determine the remote's XSIBACKUP-PRO installation point...
2019-12-29T21:50:37| Tip: should this process take too long, use the --remote-xsipath argument to set it
2019-12-29T21:50:38| Found (c) XSIBackup installation. Remote path is set dynamically
2019-12-29T21:50:38| Remote xsi path set to: none (filesystem: unknown)
2019-12-29T21:50:39| Mirroring to server 192.168.1.70 port 22
2019-12-29T21:50:39| Checking Rsync exists on the other side...
2019-12-29T21:50:39| (c)Rsync (samba.org) found at [ 192.168.1.70:22:... ]
E-mail Warnings
2019-12-29T21:50:39| The e-mail report will not be sent because of the followig reasons:
2019-12-29T21:50:39| The --mail-from string has not been set
2019-12-29T21:50:39| The --smtp-srv string has not been set
2019-12-29T21:50:39| The --smtp-port string has not been set
2019-12-29T21:50:39| The --smtp-usr string has not been set, you need --smtp-usr if --smtp-auth is other than -none-
2019-12-29T21:50:39| The --smtp-pwd string has not been set, you need --smtp-pwd if --smtp-auth is other than -none-
2019-12-29T21:50:40| Getting list of all VMs...
2019-12-29T21:50:40| 11 VEMAIL-58 [datastore1] eMail-58/eMail-58.vmx sles11_64Guest vmx-11
2019-12-29T21:50:41| 113 BBUEM-54 [datastore1] UEM-54/UEM-54.vmx windows8Server64Guest vmx-11
2019-12-29T21:50:42| 122 SightDB-185 [datastore1] tvibe-185/tvibe-185.vmx sles12_64Guest vmx-11
2019-12-29T21:50:43| 129 SightDB-185_XSIBAK [CORNEAS] SightDB-185/tvibe-185.vmx sles12_64Guest vmx-11
2019-12-29T21:50:44| 130 UNI-201_XSIBAK [CORNEAS] UNI-201/Unidata-201.vmx centos64Guest vmx-11
2019-12-29T21:50:45| 131 FLR-6_XSIBAK [CORNEAS] FLR-6/FLR.vmx sles11_64Guest vmx-09
2019-12-29T21:50:46| 137 intranet-189 [datastore1] intranet-5/intranet-5.vmx ubuntu64Guest vmx-11
2019-12-29T21:50:47| 140 survey-16 [datastore1] survey-16/survey-16.vmx ubuntu64Guest vmx-11
2019-12-29T21:50:49| 141 survey-16_XSIBAK [CORNEAS] survey-16/survey-16.vmx ubuntu64Guest vmx-11
2019-12-29T21:50:50| 153 Proxy-10 [datastore1] Proxy-10/Proxy-10.vmx ubuntu64Guest vmx-11
2019-12-29T21:50:51| 154 Proxy-10_XSIBAK [CORNEAS] Proxy-10/Proxy-10.vmx ubuntu64Guest vmx-11
2019-12-29T21:50:52| 155 Notification-4 [datastore1] MM_Notify-4/mm-40.vmx ubuntu64Guest vmx-08
2019-12-29T21:50:52| 158 BBUEM-54_XSIBAK [CORNEAS] BBUEM-54/UEM-54.vmx windows8Server64Guest vmx-11
2019-12-29T21:50:53| 159 Notification-4_XSIBAK [CORNEAS] Notification-4/mm-40.vmx ubuntu64Guest vmx-08
2019-12-29T21:50:54| 163 PHISHER-13 [datastore1] phisher-13/phisher-13.vmx ubuntu64Guest vmx-11
2019-12-29T21:50:55| 165 bbb-166 [CORNEAS] bbb-166/bbb-166.vmx ubuntu64Guest vmx-11
2019-12-29T21:50:56| 168 VEMAIL-58_XSIBAK [CORNEAS] VEMAIL-58/eMail-58.vmx sles11_64Guest vmx-11
2019-12-29T21:50:58| 7 UNI-201 [datastore1] Unidata-201/Unidata-201.vmx centos64Guest vmx-11
2019-12-29T21:50:59| 76 FLR-6 [datastore1] FLR/FLR.vmx sles11_64Guest vmx-09
2019-12-29T21:51:00| VMs to backup:
2019-12-29T21:51:00| 163 PHISHER-13 [datastore1] phisher-13/phisher-13.vmx ubuntu64Guest vmx-11
2019-12-29T21:51:06| Calculating sizes...
2019-12-29T21:51:07| [PHISHER-13] Starting backup (size is 53010M on 53008M file)
2019-12-29T21:51:07| XSIBackup will backup your VMs while they are running, so that users can continue to use the VM
2019-12-29T21:51:07| while the backup is taking place. You can also run --backup-how=cold|warm
2019-12-29T21:51:07| Hot backup selected for VM: [PHISHER-13], will not be switched off
2019-12-29T21:51:08| [PHISHER-13] info: boot partition is MBR
2019-12-29T21:51:09| Removing snapshots, please wait...
2019-12-29T21:51:11| Syncronizing config files
2019-12-29T21:51:15| [PHISHER-13] error: cannot copy VMX file, details: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:51:15| [PHISHER-13] error: cannot copy VMSD file, details: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:51:15| [PHISHER-13] info: no .vmxf file found
2019-12-29T21:51:15| [PHISHER-13] info: no .nvram file found
2019-12-29T21:51:15| [PHISHER-13] info: VMWare Tools detected, taking snapshot QUIESCED(false)...
2019-12-29T21:51:15| [PHISHER-13] info: set argument --snapshot=doquiesce to quiesce your VMs
2019-12-29T21:51:35| Backing up virtual disks...
2019-12-29T21:51:35| DISK=/vmfs/volumes/datastore1/phisher-13/phisher-13-000001-delta.vmdk
2019-12-29T21:51:35| DISK=/vmfs/volumes/datastore1/phisher-13/phisher-13-000001.vmdk
2019-12-29T21:51:35| DISK=/vmfs/volumes/datastore1/phisher-13/phisher-13-000002-delta.vmdk
2019-12-29T21:51:35| DISK=/vmfs/volumes/datastore1/phisher-13/phisher-13-000002.vmdk
2019-12-29T21:51:35| DISK=/vmfs/volumes/datastore1/phisher-13/phisher-13-Snapshot4.vmsn
2019-12-29T21:51:35| DISK=/vmfs/volumes/datastore1/phisher-13/phisher-13-Snapshot5.vmsn
2019-12-29T21:51:35| DISK=/vmfs/volumes/datastore1/phisher-13/phisher-13.vmdk
2019-12-29T21:51:35| Rsync file transfer (1st)
2019-12-29T21:51:35| From: /vmfs/volumes/datastore1/phisher-13/phisher-13-000001-delta.vmdk
2019-12-29T21:51:35| To: /vmfs/volumes/70DELL2019/20191229215033/PHISHER-13/phisher-13-000001-delta.vmdk
2019-12-29T21:51:35| [PHISHER-13] error CLRSYNC4: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:51:35| rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-12-29T21:51:35| rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
2019-12-29T21:52:36| Rsync file transfer (1st)
2019-12-29T21:52:36| From: /vmfs/volumes/datastore1/phisher-13/phisher-13-000001.vmdk
2019-12-29T21:52:36| To: /vmfs/volumes/70DELL2019/20191229215033/PHISHER-13/phisher-13-000001.vmdk
2019-12-29T21:52:36| [PHISHER-13] error CLRSYNC4: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:52:36| rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-12-29T21:52:36| rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
2019-12-29T21:52:37| Info: transfering file | /vmfs/volumes/datastore1/phisher-13/phisher-13-000001-delta.vmdk
2019-12-29T21:52:37| Info: activate your (c)XSIDiff license to boost transfer speed
2019-12-29T21:52:37| [PHISHER-13] CLXSIDF1 error: file transfer error: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:52:37| rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-12-29T21:52:37| rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
2019-12-29T21:52:37| Disk [/vmfs/volumes/datastore1/phisher-13/phisher-13-000002-delta.vmdk] excluded
2019-12-29T21:52:37| Disk [/vmfs/volumes/datastore1/phisher-13/phisher-13-000002.vmdk] excluded
2019-12-29T21:52:37| Rsync file transfer (1st)
2019-12-29T21:52:37| From: /vmfs/volumes/datastore1/phisher-13/phisher-13-Snapshot4.vmsn
2019-12-29T21:52:37| To: /vmfs/volumes/70DELL2019/20191229215033/PHISHER-13/phisher-13-Snapshot4.vmsn
2019-12-29T21:52:38| [PHISHER-13] error CLRSYNC4: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:52:38| rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-12-29T21:52:38| rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
2019-12-29T21:52:38| Rsync file transfer (1st)
2019-12-29T21:52:38| From: /vmfs/volumes/datastore1/phisher-13/phisher-13-Snapshot5.vmsn
2019-12-29T21:52:38| To: /vmfs/volumes/70DELL2019/20191229215033/PHISHER-13/phisher-13-Snapshot5.vmsn
2019-12-29T21:52:38| [PHISHER-13] error CLRSYNC4: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:52:38| rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-12-29T21:52:38| rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
2019-12-29T21:52:39| Rsync file transfer (1st)
2019-12-29T21:52:39| From: /vmfs/volumes/datastore1/phisher-13/phisher-13.vmdk
2019-12-29T21:52:39| To: /vmfs/volumes/70DELL2019/20191229215033/PHISHER-13/phisher-13.vmdk
2019-12-29T21:52:39| [PHISHER-13] error CLRSYNC4: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:52:39| rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-12-29T21:52:39| rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
2019-12-29T21:52:39| Info: transfering file | /vmfs/volumes/datastore1/phisher-13/phisher-13-flat.vmdk
2019-12-29T21:52:39| Info: activate your (c)XSIDiff license to boost transfer speed
2019-12-29T21:52:40| [PHISHER-13] CLXSIDF1 error: file transfer error: Permission denied (publickey,password,keyboard-interactive).
2019-12-29T21:52:40| rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-12-29T21:52:40| rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
2019-12-29T21:52:40| Excluded disks removed from backup .vmx file
2019-12-29T21:52:58|
2019-12-29T21:52:58| Errors detected in backup, check logs
2019-12-29T21:52:59| Backup finished
2019-12-29T21:52:59| Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup
XSIBACKUP_EXIT_STATUS=3875_ngm0yzq1ndqtmda0yi01mjewltgwntgtyjdjmdrmmzq1ytmymtu3nzyzoduxmgo
#2 Re: © OneDiff » You wont be happy with me! Brand new Dell Server » 2019-10-21 23:13:55
Here is the issue. when executing an backup to a remote server over IP, I receive this message:
"2019-10-21T23:06:58| [DOMAIN-49] error: cannot copy VMX file, details: Permission denied (publickey,keyboard-interactive)."
The target server is a exsi 6.7u3. what shall be done to correct this error?
#3 Re: © OneDiff » You wont be happy with me! Brand new Dell Server » 2019-10-21 15:23:09
Hi Let me know the best method to contact support.
Thank you
#4 © OneDiff » You wont be happy with me! Brand new Dell Server » 2019-10-20 04:32:42
- eyes
- Replies: 4
...Similar error:
###################################################################
[H[J2019-10-20T04:17:22| ###############################################################################
2019-10-20T04:17:22| XSIBACKUP-PRO 11.2.10: new execution request
2019-10-20T04:17:22| ###############################################################################
2019-10-20T04:17:22|
2019-10-20T04:17:29| NOTICE: (c) XSIBackup kills any user launched jobs, make sure you don't overlap manual jobs
XSIBackup PID: 7750122 MASTERVMH-26
Sun, 20 Oct 2019 04:17:22 +0000 IPv4: 192.168.1.27/255.255.255.0
VMware ESXi 6.0.0 build-5572656 (c) Rsync 3.1.0 as opt. dependency
Backup Id: d70 Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
2019-10-20T04:17:29| Alert: crontab is not installed for user root
2019-10-20T04:17:31| ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
2019-10-20T04:17:31| Backup user is: root
2019-10-20T04:17:31| Backup program is: onediff
2019-10-20T04:17:32| Remote OpenSSH version is: 7.9
2019-10-20T04:17:33| Negotiated Cipher (server->client): aes128-ctr
2019-10-20T04:17:33| Negotiated Cipher (client->server): aes128-ctr
2019-10-20T04:17:33| Service OpenSSH ready at server 192.168.1.70:22
2019-10-20T04:17:33| Permission denied. Please use --link-srv=remote-IP:remote-port argument to exchange keys.
#####################################################################################
Applied solution (sshd file):
# running from inetd
# Port 2200
Protocol 2
HostKey /etc/ssh/ssh_host_rsa_key
#UsePrivilegeSeparation no
# OpenSSH 7.8 switched to af21/cs1, which has been observed to cause
# connection drops. Override to earlier values.
IPQoS lowdelay throughput
# vPP FCS_SSH_EXT.1.7: rekey after 1GB, 1H (instead of default 4GB for AES)
RekeyLimit 1G, 1H
SyslogFacility auth
LogLevel info
PermitRootLogin yes
PubkeyAuthentication yes
PrintMotd yes
#PrintLastLog no
TCPKeepAlive yes
X11Forwarding no
Ciphers aes128-ctr,aes192-ctr,aes256-ctr,3des-cbc
MACs hmac-sha2-256,hmac-sha2-512,hmac-sha1
UsePAM yes
# only use PAM challenge-response (keyboard-interactive)
PasswordAuthentication yes
Banner /etc/issue
Subsystem sftp /usr/lib/vmware/openssh/bin/sftp-server -f LOCAL5 -l INFO
AuthorizedKeysFile /etc/ssh/keys-%u/authorized_keys
# Timeout value of 10 mins. The default value of ClientAliveCountMax is 3.
# Hence, we get a 3 * 200 = 600 seconds timeout if the client has been
# unresponsive.
ClientAliveInterval 200
# sshd(8) will refuse connection attempts with a probability of “rate/100â€
# (30%) if there are currently “start†(10) unauthenticated connections. The
# probability increases linearly and all connection attempts are refused if the
# number of unauthenticated connections reaches “full†(100)
MaxStartups 10:30:100
####################################################################################
Solution not working on the new server exsi 6.5.
Can you propose a solution?
Thanks
#5 © OneDiff » Strange VM Disk Path » 2019-09-21 14:48:15
- eyes
- Replies: 1
I see this strange Path in the xsiback console.
2019-09-21T10:08:16| scsi0:4.fileName = "/vmfs/volumes/adf216ff-b089449d/fs-51/fs-51_4-000001.vmdk"
for comparison:
2019-09-21T10:08:16| scsi0:0.fileName = "fs-51-000001.vmdk"
2019-09-21T10:08:16| scsi0:1.fileName = "fs-51_1-000001.vmdk"
2019-09-21T10:08:16| scsi0:2.fileName = "fs-51_2-000001.vmdk"
2019-09-21T10:08:16| scsi0:3.fileName = "fs-51_3-000001.vmdk"
2019-09-21T10:08:16| scsi0:4.fileName = "/vmfs/volumes/adf216ff-b089449d/fs-51/fs-51_4-000001.vmdk"
2019-09-21T10:08:16| scsi0:5.fileName = "fs-51_4-000001.vmdk"
How can I fix this?
Regards,
Eyes
"I see you"
#6 Re: © OneDiff » Does OneDiff have a Hard Drive copy maximum limit » 2019-09-21 14:43:10
ok. thanks.
#7 General matters » Duplicate Disks. Backup Fails! » 2019-03-04 15:19:37
- eyes
- Replies: 1
Back up failing. I noticed this weird message in the logs
"2019-03-04T14:39:17| scsi0:4.fileName = "/vmfs/volumes/adf216ff-b089449d/fs-51/fs-51_4.vmdk". The backup thinks there are duplicate disks, but that is not the case.
Any thoughts?
"Partial text from log":
2019-03-04T14:37:30| 88 fs-51_2 [datastore1] fs-51/fs-51.vmx sles11_64Guest vmx-08
2019-03-04T14:38:02| Calculating sizes...
2019-03-04T14:38:02| Needed room: 315 Gb.
2019-03-04T14:38:02| Sparse size: 1290 Gb.
2019-03-04T14:38:02| Available room: 2980 Gb.
2019-03-04T14:38:06| [fs-51_2] Starting backup (size is 323111M on 1321458M file)
2019-03-04T14:38:06| XSIBackup will backup your VMs while they are running, so that users can continue to use the VM
2019-03-04T14:38:06| while the backup is taking place. You can also run cold and warm --backup-how
2019-03-04T14:38:06| Hot backup selected for VM: [fs-51_2], will not be switched off
2019-03-04T14:38:08| [fs-51_2] info: boot partition is MBR
2019-03-04T14:38:13| [fs-51_2] notice DIFRMMIS: no [fs-51-flat.vmdk] in remote OneDiff mirror, first run?.
2019-03-04T14:38:13| [fs-51_2] notice DIFRMMIS: no [fs-51_1-flat.vmdk] in remote OneDiff mirror, first run?.
2019-03-04T14:38:13| [fs-51_2] notice DIFRMMIS: no [fs-51_2-flat.vmdk] in remote OneDiff mirror, first run?.
2019-03-04T14:38:13| [fs-51_2] notice DIFRMMIS: no [fs-51_3-flat.vmdk] in remote OneDiff mirror, first run?.
2019-03-04T14:38:13| [fs-51_2] notice DIFRMMIS: no [fs-51_4-flat.vmdk] in remote OneDiff mirror, first run?.
2019-03-04T14:38:13| [fs-51_2] notice DIFRMMIS: no [fs-51_4-flat.vmdk] in remote OneDiff mirror, first run?.
2019-03-04T14:38:13| [fs-51_2] (c) OneDiff algorithm
[fs-51_2] info: OneDiff backup first run, removing snapshots
[fs-51_2] info: all snapshots removed
2019-03-04T14:38:54| Snapshot & Quiescing
2019-03-04T14:38:54| [fs-51_2] info: VMWare Tools detected, taking snapshot QUIESCED(false)...
2019-03-04T14:38:54| [fs-51_2] info: set argument --snapshot=doquiesce to quiesce your VMs
2019-03-04T14:38:54| [fs-51_2] info: round 1
2019-03-04T14:39:02| [fs-51_2] info: snapshot taken, quiescing status:
2019-03-04T14:39:06| Removing snapshots, please wait...
2019-03-04T14:39:10| Syncronizing config files
2019-03-04T14:39:17| Backing up virtual disks...
2019-03-04T14:39:17| scsi0:0.fileName = "fs-51.vmdk"
2019-03-04T14:39:17| scsi0:1.fileName = "fs-51_1.vmdk"
2019-03-04T14:39:17| scsi0:2.fileName = "fs-51_2.vmdk"
2019-03-04T14:39:17| scsi0:3.fileName = "fs-51_3.vmdk"
2019-03-04T14:39:17| scsi0:4.fileName = "/vmfs/volumes/adf216ff-b089449d/fs-51/fs-51_4.vmdk"
2019-03-04T14:39:17| scsi0:5.fileName = "fs-51_4.vmdk"
Thank you
#8 © OneDiff » Does OneDiff have a Hard Drive copy maximum limit » 2019-01-18 01:29:06
- eyes
- Replies: 2
We have OneDiff operating on a host copying 4 VMs. One VM that we have had for many years has 6 disks:
2019-01-17T08:28:57| scsi0:0.fileName = "fs-51.vmdk"
2019-01-17T08:28:57| scsi0:1.fileName = "fs-51_1.vmdk"
2019-01-17T08:28:57| scsi0:2.fileName = "fs-51_2.vmdk"
2019-01-17T08:28:57| scsi0:3.fileName = "fs-51_3.vmdk"
2019-01-17T08:28:57| scsi0:4.fileName = "/vmfs/volumes/adf216ff-b089449d/fs-51/fs-51_4.vmdk"
2019-01-17T08:28:57| scsi0:5.fileName = "fs-51_4.vmdk"
The initial backups perform successfully and there are no glaring errors or messages. All VMs (except one) produces a _XSIBAK file. That problem VM always start the second OneDiff backup as if it's the first time OneDiff has seen it and takes hours (just like the first backup).
First Disk:
2019-01-17T08:39:32| [OESfs-51] Disk copied to /vmfs/volumes/XXXXX/OESfs-51/fs-51.vmdk
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/datastore1/fs-51/fs-51_1.vmdk'...
Second Disk:
2019-01-17T09:33:34| [OESfs-51] Disk copied to /vmfs/volumes/XXXXX/OESfs-51/fs-51_1.vmdk
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/datastore1/fs-51/fs-51_2.vmdk'...
Third Disk:
2019-01-17T10:07:33| [OESfs-51] Disk copied to /vmfs/volumes/XXXXX/OESfs-51/fs-51_2.vmdk
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/datastore1/fs-51/fs-51_3.vmdk'...
Fourth Disk:
2019-01-17T10:08:11| [OESfs-51] Disk copied to /vmfs/volumes/XXXXXOESfs-51/fs-51_3.vmdk
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/adf216ff-b089449d/fs-51/fs-51_4.vmdk'...
Fifth Disk:
2019-01-17T12:46:55| [OESfs-51] Disk copied to /vmfs/volumes/XXXXX/OESfs-51/fs-51_4.vmdk
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/datastore1/fs-51/fs-51_4.vmdk'...
Final Message:
2019-01-17T12:47:05| [OESfs-51] Disk copied to /vmfs/volumes/XXXXX/OESfs-51/fs-51_4.vmdk
2019-01-17T12:47:09| [OESfs-51] info: Updating CID at [/vmfs/volumes/XXXXX/OESfs-51/fs-51.vmdk]
2019-01-17T12:47:09| [OESfs-51] info: finished OneDiff backup, CID updated
2019-01-17T12:47:09| [OESfs-51] info: backup complete
2019-01-17T12:47:09| [OESfs-51] info: finished doing a first copy in a diff scope, subsequent backups will be differential
2019-01-17T12:47:09| [OESfs-51] info: should you need to use the mirror VM, register it manually at the backup ESXi host
Any troubleshooting ideas?
#9 Re: © OneDiff » Log Error: Permission denied (publickey,keyboard-interactive) (solved) » 2019-01-18 00:42:07
Thank you!
#10 Re: © OneDiff » Log Error: Permission denied (publickey,keyboard-interactive) (solved) » 2019-01-14 16:31:44
Hello
The remote host is manufacturer Dell Inc. ESXi 6.0.0,5572656
SSH is enabled; I can connect via putty without issue.
Thanks
#11 Re: © OneDiff » Log Error: Permission denied (publickey,keyboard-interactive) (solved) » 2019-01-14 13:37:31
Thanks for the quick reply. The response reads as follows:
###############################################################################
#
# (c) XSIBACKUP-PRO 11.2.2 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com
#
###################################################################################
NOTICE: (c) XSIBackup kills any user launched jobs, make sure you don't overlap manual jobs
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
XSIBackup PID: 863549359 r720.xxx.com
Enabling port 22 out in the ESXi firewall...
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
There is already an RSA public key at /vmfs/volumes/PE_R720/xsi-dir/xsibackup_id_rsa.pub. We will use the existing one.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enter the remote server root password when prompted.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enter remote systems's password for user root, checking OS type...
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Password:
Password:
The local RSA key has already been added to the authorized_keys file at 192.168.1.27:22.
There is no need to add it again, you should be able to connect with XSIBackup to 192.168.1.27:22 without any password.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Killed
/vmfs/volumes/50ef0839-1edef295-865c-90b11c20794a/xsi-dir #
####################################################################################
Local: exsi 5.5 (192.168.1.150)
Remote: exsi: 6.0.0 (192.168.1.27)
Thanks
#12 © OneDiff » Log Error: Permission denied (publickey,keyboard-interactive) (solved) » 2019-01-14 04:45:30
- eyes
- Replies: 6
Question #1:
We are getting this error when running a backup on a remote server:
###############################################################################
[J2019-01-14T04:18:37| ###############################################################################
2019-01-14T04:18:37| XSIBACKUP-PRO 11.2.2: new execution request
2019-01-14T04:18:37| ###############################################################################
.
2019-01-14T04:24:06| [XX-82] error: cannot copy VMX file, details: Permission denied (publickey,keyboard-interactive).
2019-01-14T04:24:07| [XX-82] error: cannot copy VMSD file, details: Permission denied (publickey,keyboard-interactive).
###############################################################################
I thought this was cosmetic, but just noticed not backups are being performed.
Question #2:
Incidentally, when i execute: >>>Key Exchange For Transparent Communication >>> List Servers Linked To This Host" the program abends and returns to the terminal prompt.
Is this a known problem?
#13 General matters » remote backup failed » 2018-10-12 15:16:36
- eyes
- Replies: 1
Hi;
Here is my log to a remote backup (below). I attempted to backup a _XSIBAK. What do you think might have happened?
++++++++++++++++++++++++++++
[H[J2018-10-12T14:44:48| ###############################################################################
2018-10-12T14:44:48| XSIBACKUP-PRO 11.0.3: new execution request
2018-10-12T14:44:48| ###############################################################################
2018-10-12T14:44:48|
2018-10-12T14:44:48| NOTICE: (c) XSIBackup kills any user launched jobs, make sure you don't overlap manual jobs
XSIBackup PID: 149998097 TTNY-2015
Fri, 12 Oct 2018 14:44:48 +0000 IPv4: 192.168.1.48/255.255.255.0
VMware ESXi 6.0.0 build-2494585 (c) Rsync 3.1.0 as opt. dependency
Backup Id: 4 Intel(R) Xeon(R) CPU E5-2623 v3 @ 3.00GHz
2018-10-12T14:44:49| Backup description: TESTFULL
2018-10-12T14:44:49| Alert: crontab is not installed for user root
2018-10-12T14:44:50| ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
2018-10-12T14:44:50| Backup user is: root
2018-10-12T14:44:50| Backup program is: vmkfstools
2018-10-12T14:44:51| --backup-point found at /vmfs/volumes/HONEY48/INCREMENTAL (filesystem: NFS)
E-mail Warnings
2018-10-12T14:44:51| The e-mail report will not be sent because of the followig reasons:
2018-10-12T14:44:51| The --mail-from string has not been set
2018-10-12T14:44:51| The --smtp-srv string has not been set
2018-10-12T14:44:51| The --smtp-port string has not been set
2018-10-12T14:44:51| The --smtp-usr string has not been set, you need --smtp-usr if --smtp-auth is other than -none-
2018-10-12T14:44:51| The --smtp-pwd string has not been set, you need --smtp-pwd if --smtp-auth is other than -none-
2018-10-12T14:44:52| Getting list of all VMs...
2018-10-12T14:44:52| 107 server1-188 [datastore1] server1/server1.vmx sles11_64Guest vmx-08
2018-10-12T14:44:53| 108 server2-187 [datastore1] server2-187/server2-189.vmx sles11_64Guest vmx-08
2018-10-12T14:44:54| 11 server3-58 [datastore1] server3-58/eMail-58.vmx sles11_64Guest vmx-11
2018-10-12T14:44:56| 113 server4-54 [datastore1] server4-54/server4-54.vmx windows8Server64Guest vmx-11
2018-10-12T14:44:57| 122 server5-185 [datastore1] server5-185/server5-185.vmx sles12_64Guest vmx-11
2018-10-12T14:44:59| 7 server6 [datastore1] server6-201/server6-201.vmx centos64Guest vmx-11
2018-10-12T14:45:00| 76 server7-6 [datastore1] server7/FLR.vmx sles11_64Guest vmx-09
2018-10-12T14:45:02| 81 server8-145 [SAFETY] 48vmbackups2/server8-145/VW2k-145-2018-02-24_21-28-32/server8.vmx win2008ServGuest vmx-07
2018-10-12T14:45:03| Error NOVM2BAK: no VMs to backup
2018-10-12T14:45:04| [ALL VMs] info: no directories to delete as per the --del-dirs argument
ls: /vmfs/volumes/dd2620b4-ddfd0aa2: Input/output error
2018-10-12T14:45:06| The ESXi configuration was saved to "/vmfs/volumes/HONEY48/INCREMENTAL/20181012144448"
sh: bad number
sh: bad number
sh: bad number
2018-10-12T14:45:06| Backup finished
2018-10-12T14:45:06| Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup
XSIBACKUP_EXIT_STATUS=0_ndq0ntrjngmtntkwmc0xmdmxltgwmzetyjzjmdrmntm0odmxmtuzotm1ntu1oao
#14 General matters » List Server Linked to this Host- exits unexpectedly » 2018-10-12 14:06:08
- eyes
- Replies: 1
Hi:
here is what i noticed: when I choose the above option in the gui the program ends expectantly and returns to the terminal prompt. A reboot does not fix the issue.
When I choose "Add this host to the remote server" I can see that the server is already added.
Let me know if you have a workaround or fix.
Thanks
#15 Re: General matters » [VMKFSTOOLS] Unable to Disable "COLD" backup (GUI). » 2018-10-12 13:21:00
All is resolved. We rebooted the host and the backup worked as designed. Thanks for the response.
#16 Re: General matters » [VMKFSTOOLS] Unable to Disable "COLD" backup (GUI). » 2018-10-11 19:10:57
Here is my configuration from my xsi-dir>jobs folder:
"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-prog=Vmkfstools \
--date-dir=yes \
--backup-point=/vmfs/volumes/DMZ/BACK_FULL \
--backup-type=All \
--backup-how=Hot \
--del-dirs=+3d \
--backup-id=2 \
--description="full backup test" \
--snapshot=doquiesce \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup.log"
#17 General matters » [VMKFSTOOLS] Unable to Disable "COLD" backup (GUI). » 2018-10-11 18:52:59
- eyes
- Replies: 3
Hello:
I'm working in the GUI interface. When I step through the menus the "Cold" option has an asterisks next to that option by default. I do not want the VM to reboot.
I can seem to be able to remove this option. It seems "Hot" and "Cold" can be set at the same time. I can not seem to add the screen grab.
Is there a workaround?
#18 Re: General matters » gui setup (daily incremental - full every 3 days) » 2018-10-11 18:44:11
Thank you.
#19 Re: General matters » gui setup (daily incremental - full every 3 days) » 2018-10-10 16:43:53
Hi,
Thanks for your quick reply. Is it safe to say that if I use vmkfstools behind onediff I should only backup the XXXX_xsibak file with vmkfstools?
Thanks again.
#20 General matters » gui setup (daily incremental - full every 3 days) » 2018-10-10 09:29:34
- eyes
- Replies: 4
Hello:
Using the GUI interface exclusively, We would like to learn the steps for setting up an incremental backup and fullback to different subfolders on the same datastore.
Subfolder (full and incremental). The backups should be chained with the Full occurring every 3 days.
Thanks!
#21 Re: General matters » Guidance for Backup Process » 2018-03-21 19:39:56
Thanks again for helping with the backup scripts. I have one follow-up question:
We noticed that hours after we ran the onediff script, some vm's left an unconsolidated snapshot and other did not. What is the normal behavior?
Thanks again
#22 Re: General matters » Guidance for Backup Process » 2018-03-16 21:36:30
Excellent Feedback. Thank you! You made my weekend. Have a great weekend.
Eyes
#23 Re: General matters » *_XSIBAK what is this file used for? » 2018-03-16 21:33:32
Very comprehensive article. Thank you very much. Anxiety relived.
#24 General matters » *_XSIBAK what is this file used for? » 2018-03-16 01:51:10
- eyes
- Replies: 2
I performed a backup with XSIBackup-Pro. When the backup was completed I found files (that looks like VM in an off state) next to active VMs.
What are these items and what are they used for?
What happens if deleted?
Thanks
#25 General matters » Guidance for Backup Process » 2018-03-14 22:20:22
- eyes
- Replies: 4
Greetings!
We are a new XSIBackupPro user having converted from GhettoVCB. With GhettoVCB we created full backups everyday -- twice a day.
Our environment is as following:
Four EXSi Server having VM's stored locally to the server. The backups are transmitted to a NAS Box (LAN) connected to the same VMHost.
We have the following Wish List:
1) Create two (2) separate incremental backups everyday Monday-Sunday. The first incremental backup will start at Midnight, while the second incremental backup will start at Noon) to NAS Drive1 . The idea is to speed up the backups during the week.
2) Create one separate FULL backup on Sunday to NAS Drive2 When the Office Closed. The idea is to take this drive off-site on Monday.
3) Compression would be an added Benefit.
How can i convert our current working script (below) to accomplish the items in the Wish List above as close as possible.
Our current working Cron script:
/vmfs/volumes/datastore1/xsi-dir/xsibackup --time="Mon 22:00|Tue 22:00|Wed 22:00|Thu 22:00|Fri 22:00|Sat 22:00|Sun 22:00" --backup-point="/vmfs/volumes/DMZ" --backup-how=hot --backup-type=all --mail-from=server@chop.us --mail-to=chicken@chop.us --smtp-srv=192.168.9.66 --smtp-port=25 --smtp-usr=pork@chop.us --smtp-pwd=busybox --date-dir=yes --shell-warnings=0 --smart-info=yes --del-dirs=+3d
Thanks in advance for your information.
Follow-up questions:
Considering that the above Wish List can be accomplished:
1) In the event a Production VM Host goes down, will I be able to attach a Backup VM Host to the NAS with an incremental backup and have full functionality of the VM?
Thanks again for your information.
eyes
- Index
- » Search
- » Posts by eyes