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 8E5F39A15 for <pve-user@lists.proxmox.com>; Fri, 4 Aug 2023 11:06:28 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7015CC546 for <pve-user@lists.proxmox.com>; Fri, 4 Aug 2023 11:06:28 +0200 (CEST) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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>; Fri, 4 Aug 2023 11:06:27 +0200 (CEST) Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-51a52a7d859so6338210a12.0 for <pve-user@lists.proxmox.com>; Fri, 04 Aug 2023 02:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691139980; x=1691744780; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=IMa4KK+xAernPFXI3N0WvCgbeR3juEtxkNP1llnE99I=; b=rdiFwpiNsYRImc1Bt7AqtoeImCpRC0JUyV6gzTaFWAX76KFer4nbD4cRKKM78i9STY W0v71tQ9o4bvPE9fF4oRdPscq3BDy2d9KDu3McaGNkLxC9Wdp/mHHXtKE6lW9/E/pvzy n4OO35kN3XH5dkK/uMl6tKXs9vJyt2K2vT320ZWnqP6bZ6Ows4mxr6iTcXN/rkEWlnVj +R9MaRqhLUyhxvohF9DVI8pAroNtEIkyVW9W2pvqCI+fQyA3HIa5qChECXrjMJQPgXh8 nX8P8/GAChV8rlF0rdpicxeVHPzWGLR3DoqAHyrcBDJVIIcpLmcr+7meQxSOKz/EDA61 0WEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691139980; x=1691744780; h=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=IMa4KK+xAernPFXI3N0WvCgbeR3juEtxkNP1llnE99I=; b=Wtg/qV4/R1l+bnrUS6Y7GZGUAAYnCQUylgit43hF8yciSoewRmVWHxChr5uQSLYygf HcRbxldKQOV8Z7chXBJTFcNam/vyiowCmoDUqm6ehdjW1JXL6Je1XlEYtF7c4VUy+Pln 1uV1VGaWkIKLJIFbJ3nRFsoASGf4Tvnh9r99us0TmBNuyMGVR9YY2gG5rDD7hzpRyVQ3 jENR1m9mx7zzafP4NGMYA/M+bOg9wQpP3RHiWMYvkciBTBsd3iO/auq1W6PE1eakgz1B kEG5YIvoJgSItytYXiYg5ruDtdjfOTN/UFo4YF4Dll3JXAnVhdRiWE50r1oPv66v3y2H xMHg== X-Gm-Message-State: AOJu0Yyses4v+SzfylIbczP7pvLMb5hvnLVqPJf0Za7IVQaZ+geGcvNK MaEY6ogEN76YNJjZaKdZFXr7haGjgESqzcMO6P9uRoWa5RI= X-Google-Smtp-Source: AGHT+IG3MZGj1C56eYG2KOwbviylnykn9yoIF0XkA6lSOUPkuuL9kxu08mHeCYyFfjRXbc1HI2skoHdLAH9HiI8vAr0= X-Received: by 2002:a05:6402:4305:b0:51e:5206:d69e with SMTP id m5-20020a056402430500b0051e5206d69emr1344190edc.10.1691139980314; Fri, 04 Aug 2023 02:06:20 -0700 (PDT) MIME-Version: 1.0 References: <CAKeuxjDvTrDTQtNsiNYiBg0H5Lm6UQWVSMXNygbKVPQ7hJhRMg@mail.gmail.com> <87f8a99d-fe4a-815a-4213-61e7668cf8f8@proxmox.com> <CAKeuxjBewy7eZM-Z4uGWDqptLbFogbjcM7VL+=wo7SuOcdQ_Lw@mail.gmail.com> <1bab43c9-edf3-9a3a-c5f6-0d9b0aee1de6@unibe.ch> In-Reply-To: <1bab43c9-edf3-9a3a-c5f6-0d9b0aee1de6@unibe.ch> From: Joseph John <jjk.saji@gmail.com> Date: Fri, 4 Aug 2023 13:06:08 +0400 Message-ID: <CAKeuxjAGy-aNtZaOgivwWyx=3GrotN7d2O6JLH7=v_u=v6XoiA@mail.gmail.com> To: Proxmox VE user list <pve-user@lists.proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.488 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 NUMERIC_HTTP_ADDR 1.242 Uses a numeric IP address in URL POISEN_SPAM_PILL_4 0.1 random spam to be learned in bayes 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 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] 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: Fri, 04 Aug 2023 09:06:28 -0000 Hi , Thanks for the advice I tried first with a CIFS share , checked by accessing it from other machines . created CIFS share (Left hand side of menu, Data Center, Storage) , Now when I go to the VM , backup option , and click backup I can only see the local storage, I am not able to see the CIFS share which I created Similarly I did with NFS server and shared directory , checked it by accessing it from other hosts. Created NFS share (Left hand side of menu, Data Center, Storage). This also when I go the the VM, backup option and click back I can only see the local storage , not the NFS or the CIFS storage which we created earlier . The prox mox version is 6.3-3. But when I give a df-h , I get the results oot@server-1:~# df -h Filesystem Size Used Avail Use% Mounted on udev 378G 0 378G 0% /dev tmpfs 76G 13M 76G 1% /run /dev/mapper/pve-root 29G 6.2G 22G 23% / tmpfs 378G 69M 378G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 378G 0 378G 0% /sys/fs/cgroup /dev/sdb2 511M 312K 511M 1% /boot/efi /dev/fuse 30M 72K 30M 1% /etc/pve *//10.115.129.160/proxmox <http://10.115.129.160/proxmox> 1.0T 359G 666G 36% /mnt/pve/backup10.115.129.169:/home/itsupport/nfsshare 1017G 14G 955G 2% /mnt/pve/nfsbackup* tmpfs 76G 0 76G 0% /run/user/0 So from the df -h , we can see the CIFS and NFS, but through the web interfaces, backup option do not show them in the drop down menu. I am thinking in this situation, to make use command line and run the backup so that I can specify the location (cifs or nfs share) to which I can copy the disk image I will be posting another thread on requesting on how to use command line to take backup of VM images Thanks Joseph John On Thu, Aug 3, 2023 at 7:14=E2=80=AFPM Peppo Brambilla <peppo.brambilla@uni= be.ch> wrote: > 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 ne= w > > 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 cep= h > > 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@prox= mox.com> > > 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 cluster= s > >> 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 imag= e > >>> > >>> > >>> 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 enterpri= se > >>> 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=C3=A4t Bern > Phil.-nat. Fakult=C3=A4t > Institut f=C3=BCr Informatik > > Dr. Peppo Brambilla > Systemadministrator > > Neubr=C3=BCckstrasse 10 > 3012 Bern > Schweiz > Telefon +41 31 684 33 10 > > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >