From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 0041A982E for ; Thu, 3 Aug 2023 17:14:01 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DC50C5E7F for ; Thu, 3 Aug 2023 17:14:01 +0200 (CEST) Received: from mailhub-lb3.unibe.ch (mailhub-lb3.unibe.ch [130.92.1.142]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 ; Thu, 3 Aug 2023 17:14:00 +0200 (CEST) X-Virus-Scanned: By University of Bern - MGW Received: from mail.campus.unibe.ch (aai-edge-03.campus.unibe.ch [130.92.13.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhub-lb3.unibe.ch (Postfix) with ESMTPS id 16859500091 for ; Thu, 3 Aug 2023 17:08:26 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unibe.ch; s=mgwsel1; t=1691075306; bh=Wju73T7ER8CpAlMoobgRllExLoueiFw5qhbR1S+mTUE=; h=Date:To:References:From:Subject:In-Reply-To:From; b=e1+BIym7hAVm+AIUoS+cKY5cxhTmikr4hi62aijwl/DUKoJIS9H0WJulOJHPneSVz hoTwDpBF2wz04oU0ymtH+tTTu6gDiIzG1uFxNT3z9vvI47POjdJ3BRNSPl88XurLd8 NG2sjv40TT16+jyba6FHpU4OlZt6exfRbe3ZtXtS3grwrqNUg7WkSxmkk8srWDK1jM FdNpomSljO4L+mdmx6BjSo50TpdpHhK9MhEUldn51Su5URkV2t37MXf9SlKwJEJ2WK zZwIv0tol9YL9hKXXGp+UG5dt13R+3A1v+P8sQ3hEIDZ6/PEITukAEr7LS4zl5euJr r2NbsLCTKD+ow== Received: from aai-mail-01.campus.unibe.ch (130.92.13.40) by AAI-EDGE-03.campus.unibe.ch (130.92.13.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.2507.27; Thu, 3 Aug 2023 17:08:17 +0200 Received: from [130.92.64.89] (130.92.64.89) by aai-mail-01.campus.unibe.ch (130.92.13.40) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.2507.27; Thu, 3 Aug 2023 17:08:25 +0200 Message-ID: <1bab43c9-edf3-9a3a-c5f6-0d9b0aee1de6@unibe.ch> Date: Thu, 3 Aug 2023 17:08:25 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1 Content-Language: en-GB To: References: <87f8a99d-fe4a-815a-4213-61e7668cf8f8@proxmox.com> From: Peppo Brambilla In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [130.92.64.89] X-ClientProxiedBy: aai-mail-03.campus.unibe.ch (130.92.13.41) To aai-mail-01.campus.unibe.ch (130.92.13.40) X-SPAM-LEVEL: Spam detection results: 0 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 KAM_ASCII_DIVIDERS 0.8 Email that uses ascii formatting dividers and possible spam tricks NICE_REPLY_A -0.102 Looks like a legit reply (A) 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 - 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Aug 2023 15:14:02 -0000 Hi I was using an NFS server connected to the old and new cluster. This should be setup as similar as possible on both cluster. Maybe it's sufficient if they are named the same. Then I proceeded as follows: * move VM's disks to the NFS share * shutdown VM on old cluster * copy VM's config files in /etc/pve/qemu-server/  from old to new server * you should now see the VM on the new server as well * start VM on new server * move disks of VM to ceph on new server (you may want to keep the old disk images) * if the VM runs fine, you can remove the config files on the old cluster and remove the disk images there as well) Cheers -- Peppo On 03.08.23 11:19, Joseph John wrote: > 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 AM Aaron Lauterer > wrote: > >> That sounds like a reasonable plan. >> >> If you have a network share that you want to utilize for the backups later >> 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 decommissioning >> 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 is >>> going on. >>> >>> Earlier we were using ProxMox 6.X Community Edition, this is a separate >>> unit which we were using . Now once the enterprise edition is up, we plan >>> 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 >>> >>> >> > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user -- Universität Bern Phil.-nat. Fakultät Institut für Informatik Dr. Peppo Brambilla Systemadministrator Neubrückstrasse 10 3012 Bern Schweiz Telefon +41 31 684 33 10