BrokeDBA

backup-vm1-20200226-08-58-26.log

Mar 1st, 2020
75
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. [root@/opt/ovm-bkp/logs]# more backup-vm1-20200226-08-58-26.log
  2. =================
  3. Oracle VM 3.4 CLI
  4. =================
  5. =====================================================
  6. Adding VM vm1 information to bkpinfo file /opt/ovm-bkp/bkpinfo/info-backup-vm1-FULL-20200226-0858.txt
  7. =====================================================
  8. ./ovm-backup.sh: line 273: [: OVM>: integer expression expected
  9. ================================================
  10. Creating Clone-Customizer to get VM snapshot....
  11. ================================================
  12. OVM> create VmCloneCustomizer name=vDisks-vm1-20200226-0858 description=vDisks-vm1-20200226-0858 on Vm name=vm1
  13. Command: create VmCloneCustomizer name=vDisks-vm1-20200226-0858 description=vDisks-vm1-20200226-0858 on Vm name=vm1
  14. Status: Success
  15. Time: 2020-02-26 08:58:47,940 EST
  16. JobId: 1582725527174
  17. Data:
  18.   id:0004fb0000130000e0bb903e83c3fb23  name:vDisks-vm1-20200226-0858
  19. OVM> Connection closed.
  20. OVM> create VmCloneStorageMapping cloneType=THIN_CLONE name=vDisks-Mapping-0004fb00001300007fad4d06b10a887b vmDiskMapping=0004fb00001300007fad4d06b10a887b repository=vmdata on VmCloneCustom
  21. izer name=vDisks-vm1-20200226-0858
  22. Command: create VmCloneStorageMapping cloneType=THIN_CLONE name=vDisks-Mapping-0004fb00001300007fad4d06b10a887b vmDiskMapping=0004fb00001300007fad4d06b10a887b repository=vmdata on VmCloneCu
  23. stomizer name=vDisks-vm1-20200226-0858
  24. Status: Success
  25. Time: 2020-02-26 08:58:51,282 EST
  26. JobId: 1582725530688
  27. Data:
  28.   id:0004fb000013000001b92fbdc3768cc7  name:vDisks-Mapping-0004fb00001300007fad4d06b10a887b
  29. OVM> Connection closed.
  30. =======================
  31. Getting VM snapshot....
  32. =======================
  33. OVM> clone Vm name=vm1 destType=Vm destName=vm1-CLONE-20200226-0858 ServerPool=OVM-Lab cloneCustomizer=vDisks-vm1-20200226-0858
  34. Command: clone Vm name=vm1 destType=Vm destName=vm1-CLONE-20200226-0858 ServerPool=OVM-Lab cloneCustomizer=vDisks-vm1-20200226-0858
  35. Status: Failure
  36. Time: 2020-02-26 08:58:55,296 EST
  37. JobId: 1582725533848
  38. Error Msg: Job failed on Core: OVMRU_007013E Cannot thin clone: EHealth_vdisk1, to: vmdata. The clone target does not support thin cloning. [Wed Feb 26 08:58:54 EST 2020]
  39. OVM> Connection closed.
  40. OVM> delete VmCloneCustomizer name=vDisks-vm1-20200226-0858
  41. Command: delete VmCloneCustomizer name=vDisks-vm1-20200226-0858
  42. Status: Success
  43. Time: 2020-02-26 08:58:57,299 EST
  44. JobId: 1582725536654
  45. OVM> Connection closed.
  46. =====================
  47. Backup Type: FULL....
  48. =====================
  49. OVM> create VmCloneCustomizer name=vm1-20200226-0858 description=vm1-20200226-0858 on Vm name=vm1-CLONE-20200226-0858
  50. Command: create VmCloneCustomizer name=vm1-20200226-0858 description=vm1-20200226-0858 on Vm name=vm1-CLONE-20200226-0858
  51. Status: Failure
  52. Time: 2020-02-26 08:58:58,441 EST
  53. Error Msg: Couldn't find a Vm object with the identifier of vm1-CLONE-20200226-0858.
  54. OVM> Failed to complete command(s), error happened. Connection closed.
  55. =======================================================
  56. Moving cloned VM to target repository ....
  57. =======================================================
  58. OVM> moveVmToRepository Vm name=vm1-CLONE-20200226-0858 CloneCustomizer=vm1-20200226-0858 targetRepository=vmdata
  59. Command: moveVmToRepository Vm name=vm1-CLONE-20200226-0858 CloneCustomizer=vm1-20200226-0858 targetRepository=vmdata
  60. Status: Failure
  61. Time: 2020-02-26 08:59:01,677 EST
  62. Error Msg: Couldn't find a Vm object with the identifier of vm1-CLONE-20200226-0858.
  63. OVM> Connection closed.
  64. =======================================================
  65. Waiting for Vm moving to complete......10 seconds
  66. ....
  67. ...
  68. Waiting for Vm moving to complete......39320 seconds
Add Comment
Please, Sign In to add comment