XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. sumansaha
    3. Posts
    S
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 33
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Snapshot failure

      @sumansaha
      Hello Team,
      The issue has resolved after applying xe-toolstack-restart.
      Thanks.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Snapshot failure

      @sumansaha As the issue is not only with XO. I can create the discussion again out of XO.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: increase 24 hour timeout-limit on backup/copy

      @sumansaha BTW , The issue was fix with a workaround. I've used another XOA where the interface was 1Gbps, Source XCP-NG--->XOA---> Destination SR all were 1Gbps . In that case transfer time has significantly dropped to 5 hours. For continuous replication, from source data stream come to XOA at first and then to the destination.Here I had a misconception , I was thinking backup data directly send to destination from Source XCP-NG.Thanks everyone for your help always.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Snapshot failure

      @olivierlambert BTW new finding is , we also can't connect the XCP-NG with XCP-NG center. That mean the issue is with the XCP-NG server.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: increase 24 hour timeout-limit on backup/copy

      @olivierlambert Aha That make sense. Let me update my XO.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Snapshot failure

      @olivierlambert suman@xoa:~$ wget --no-check-certificate https://192.168.196.99
      --2023-06-27 17:34:59-- https://192.168.196.99/
      Connecting to 192.168.196.99:443... connected.
      WARNING: cannot verify 192.168.196.99's certificate, issued by ‘CN=xcp-ng-ohiphxpk’:
      Self-signed certificate encountered.
      WARNING: certificate common name ‘xcp-ng-ohiphxpk’ doesn't match requested host name ‘192.168.196.99’.
      Failed writing HTTP request: Connection reset by peer.
      Retrying.

      It is not accessible through the URL.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: increase 24 hour timeout-limit on backup/copy

      @florent XO is not updated.
      I was seeing progress when the backup process was running. 96% was completed . It has dropped on that status.
      How I can enable NBD.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Snapshot failure

      @Darkbeldin It was not updated nor rebooted actually.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: increase 24 hour timeout-limit on backup/copy

      @florent 2023-06-25T18_30_22.009Z - backup NG.txt

      the log file is attached according to your requirement.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Snapshot failure

      @Darkbeldin Screenshot 2023-06-27 at 2.51.35 PM.png Screenshot 2023-06-27 at 2.52.48 PM.png

      Yes its showing the error as attached.But from XOA server we can SSH to XCP-NG without any issue.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Snapshot failure

      @sumansaha Even after that XOA can't connect with the XCP-NG . But from XOA we can SSH to the XCP-NG. Any help would be great.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: increase 24 hour timeout-limit on backup/copy

      @olivierlambert ![alt text](Screenshot 2023-06-27 at 1.11.18 PM.png Screenshot 2023-06-27 at 1.09.30 PM.png image url)

      I'm sending the XCP-NG(Source) VM backup to another XCP-NG(Destination) storage using XOA. I've changed the value of pending_task_timeout to 72 hours in source XCP-NG. Still the backup ended just after 24 hours.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: increase 24 hour timeout-limit on backup/copy

      @olivierlambert I've changed the value to 72 hours in source XCP-NG but it doesn't work at all.

      posted in Xen Orchestra
      S
      sumansaha
    • Snapshot failure

      ECONNRESET when I'm attempting to take a snapshot. Can you please help on that how I can resolve the issue.

      vm.snapshot
      {
        "id": "f0a8e6be-3XXX-2XXX-b6ee-c86f7830f479"
      }
      {
        "errno": "ECONNRESET",
        "code": "ECONNRESET",
        "syscall": "write",
        "url": "https://192.168.196.99/jsonrpc",
        "call": {
          "method": "VM.get_record",
          "params": [
            "OpaqueRef:94f9af77-0baf-4799-bd0f-64a123d2d073"
          ]
        },
        "message": "write ECONNRESET",
        "name": "Error",
        "stack": "Error: write ECONNRESET
          at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:94:16)"
      }
      
      posted in Xen Orchestra
      S
      sumansaha
    • RE: Max duration for Backup

      I've added the backup task as continuous replication and taking the backup in a NAS. Screenshot 2023-01-29 at 4.06.58 PM.png image url)

      posted in Xen Orchestra
      S
      sumansaha
    • Max duration for Backup

      I've added backup task for one VM. The VM size is 1000GB. Back up task stopped just after 24 hours . Is there any default duration for backup . How I can increase the back up duration.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Control domain of Xcp-ng

      @olivierlambert How we can troubleshoot that.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Control domain of Xcp-ng

      @olivierlambert
      Screenshot 2023-01-05 at 11.46.17 AM.png

      Thanks for your response.After 'Destory VDI' from Disk currently there is only one base copy. And no coalesced process running now. Is there any way to remove current base copy.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Control domain of Xcp-ng

      @olivierlambert Screenshot 2023-01-05 at 2.16.07 AM.png

      There is no snapshot actually. Should I run "Destroy VDI" on the snapshots from the disk.

      posted in Xen Orchestra
      S
      sumansaha
    • RE: Control domain of Xcp-ng

      @olivierlambert Screenshot 2023-01-05 at 2.02.59 AM.png

      I've disconnected the snapshots and after that should I go for to Destroy VDI' .

      posted in Xen Orchestra
      S
      sumansaha