From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <jjk.saji@gmail.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id BB2279534 for <pve-user@lists.proxmox.com>; Thu, 3 Aug 2023 11:19:26 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9C0B41FEFE for <pve-user@lists.proxmox.com>; Thu, 3 Aug 2023 11:19:26 +0200 (CEST) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Thu, 3 Aug 2023 11:19:24 +0200 (CEST) Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-99bf8e5ab39so101983666b.2 for <pve-user@lists.proxmox.com>; Thu, 03 Aug 2023 02:19:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691054358; x=1691659158; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XMhcc5w0HwTbYwN3KDl/ZYFRuyQEC7po1w+diBO701A=; b=pfmPJdRJjv5jlOr6FA2n7U2gsT276LzTUy9h9Vugl2beIqfjx7qCyo3pNSTLn+bbwz JSSc1kieMUPW4AiSS1qw4TidLNbX93q/5b+sze8RY+ragDtgGLg/RqjP2Gbno7LdSLGR J9x+y5NsbfuqPojH4Vmm6Wz2BQvtO0naX4/ZeIeRm76CFd42z83xbrv/4/zIQWqnnTcu xgH2dtfFjTIpFaw/Sg0olZXdNO6u/Jj9g9RS+nmssjMu6niwgZAC+mHxbC3ljdfOhsyf 7lEdsfH1aWXOk/xtLHN0RjZUTDkOE5O2y9Qq04gFWQ7it3UGm+mpxivWhvc47DlYt6vT DoDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691054358; x=1691659158; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XMhcc5w0HwTbYwN3KDl/ZYFRuyQEC7po1w+diBO701A=; b=d/n/gBgbZ/nf8oLOrkOaSIhNZsXP10gkF6ZsEvXNJ84LtD71uyOPCkyBBWYT3VnNS6 pu3wBdUhL7q6evzqHl2rmHlQBlmcYEf3BHokynhCnY1JEvP2tIOEJQAKZy74UkW2uRXX EDlx4o0ZaP97UcJ2rYcPSPRPjPbL5uYxkn7wdK2yQlgAE7iXqIjqyf8mJR/wELwyCK+y eb8+T+gGeRIYim5/V8Bs771it5G/T0OTM2g2sB+blQapisKWK4lbMG0bexD7oTA8wehq liPm+Q06Q9xPn1fqIiVVartOy8QLJJBrNtctsTGDXipqOSNlsQ3GTHT9OFB3d1c6BlY2 wBNA== X-Gm-Message-State: ABy/qLahJvxp3G0jYCn9VuqIlNTPxzCh/Ap8YQHTIplHdkK/F7hU/mrm 9j4lFOfHigu69sASsRUV4sfsYMtB4YORwGEGDO0osZnpMF6OFQ== X-Google-Smtp-Source: APBJJlH6B4DSQu3owMG8qRDjVc03WZ6BGb7EWX1UZgm6c1zduc1J3pc5C8rK5BZ+DyE9nzADu3rSf8k0e5VcTrekcXI= X-Received: by 2002:a17:906:57:b0:99b:d1d8:d74d with SMTP id 23-20020a170906005700b0099bd1d8d74dmr7215496ejg.45.1691054358269; Thu, 03 Aug 2023 02:19:18 -0700 (PDT) MIME-Version: 1.0 References: <CAKeuxjDvTrDTQtNsiNYiBg0H5Lm6UQWVSMXNygbKVPQ7hJhRMg@mail.gmail.com> <87f8a99d-fe4a-815a-4213-61e7668cf8f8@proxmox.com> In-Reply-To: <87f8a99d-fe4a-815a-4213-61e7668cf8f8@proxmox.com> From: Joseph John <jjk.saji@gmail.com> Date: Thu, 3 Aug 2023 13:19:06 +0400 Message-ID: <CAKeuxjBewy7eZM-Z4uGWDqptLbFogbjcM7VL+=wo7SuOcdQ_Lw@mail.gmail.com> To: Aaron Lauterer <a.lauterer@proxmox.com> Cc: Proxmox VE user list <pve-user@lists.proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.194 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] Moving virtual machine from CE 6.X to latest enterprise edition, advice requested X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Thu, 03 Aug 2023 09:19:26 -0000 Hi Thanks. The backup option for some reason not completing successfully from the log files cat /var/lib/vz/dump/vzdump-qemu-109-2023_08_02-12_34_08.log 2023-08-02 12:42:10 ERROR: vma_queue_write: write error - Broken pipe 2023-08-02 12:42:10 INFO: aborting backup job 2023-08-02 12:42:10 INFO: stopping kvm after backup task 2023-08-02 12:42:13 ERROR: Backup of VM 109 failed - vma_queue_write: write error - Broken pipe the GUI /Web way of taking backup not working I have to find another way of taking the image and putting it on the new setup , the present one storage is based on the ceph storage and the vm are in the ceph pook I am thinking a way in which I can try to take to VM image from the ceph pool and move it to the other new pve instance Guidance requested for getting the vm images to new proxmox Thanks Joseph John On Wed, Aug 2, 2023 at 11:37=E2=80=AFAM Aaron Lauterer <a.lauterer@proxmox.= com> wrote: > That sounds like a reasonable plan. > > If you have a network share that you want to utilize for the backups late= r > on > (never store them on the same machine, 3-2-1 backup strategy and such ;) = ) > you > could already configure it on the old Proxmox VE server. That way, you > don't > have to manually move the backup files over. Since you are decommissionin= g > the > old server, there is no risk of running into issues of two different > Proxmox VE > clusters (or separate single nodes), accessing the exact same storage. > > Under normal situations, you don't want to give two Proxmox VE clusters > access > to the same storage, as you might run into VMID conflicts. > > Cheers, > Aaron > > On 8/2/23 09:31, Joseph John wrote: > > Dear All, > > Good morning > > We are going to have ProxMox 8 enterprise edition setup, installation i= s > > going on. > > > > Earlier we were using ProxMox 6.X Community Edition, this is a separat= e > > unit which we were using . Now once the enterprise edition is up, we pl= an > > to move all the VM instance which were on the old 6.X CE to the > separate > > ProxMox 8 enterprise edition > > > > I am planning to move the old vm form the CE (6.X) to ProxMox 8 > (Enterprise > > Edition) in the following way > > > > - Take backup of the VM at CE using the backup option > > - scp/rsync the backup files to the Prox Mox 8 Enterprise version > > - Use the restore option from the new server to restore the image > > > > > > Like to get advice, if the above mentioned steps is apt when you are > going > > to move from one of the older CE edition [6.X] to the latest enterprise > > edition > > > > Thanks > > Joseph John > > _______________________________________________ > > pve-user mailing list > > pve-user@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > > >