Re: [PVE-User] Backup/timeout issues PVE 6.4

["Сергей Цаболов" <tsabolov@t8.ru>]

I have the same case with backup.

7 Nodes mount the same NFS path on Synology (folder)

But? I make the In backup settings some groups (every group is node 
1,2,3 etc and is VM) and set the time backups on groups, not the same time.

And the Mode of backup is Compression is ZSTD, Snapshot.

See screenshot.


19.04.2022 18:07, Eneko Lacunza пишет:
>
> Yes, all nodes mount the same NFS export.
>
> El 19/4/22 a las 16:52, Сергей Цаболов escribió:
>>
>> The Synology path mount over NFS is shared on 3 nodes ?
>>
>> 19.04.2022 17:46, Eneko Lacunza via pve-user пишет:
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user@lists.proxmox.com
>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
Sergey TS
The best Regard
______________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
From elacunza@binovo.es  Tue Apr 19 18:08:04 2022
Return-Path: <elacunza@binovo.es>
X-Original-To: pve-user@lists.proxmox.com
Delivered-To: pve-user@lists.proxmox.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 B727BDC25
 for <pve-user@lists.proxmox.com>; Tue, 19 Apr 2022 18:08:04 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id AA2AF3000
 for <pve-user@lists.proxmox.com>; Tue, 19 Apr 2022 18:08:04 +0200 (CEST)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com
 [IPv6:2a00:1450:4864:20::436])
 (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 id B5AEF2FEF
 for <pve-user@lists.proxmox.com>; Tue, 19 Apr 2022 18:08:03 +0200 (CEST)
Received: by mail-wr1-x436.google.com with SMTP id w4so23082325wrg.12
 for <pve-user@lists.proxmox.com>; Tue, 19 Apr 2022 09:08:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=binovo.es; s=google;
 h=message-id:date:mime-version:user-agent:subject:content-language:to
 :references:from:in-reply-to;
 bh=AgxyHPZj2rmpF42w7ta8fWoHOf6FCAdTgeFY5CKavtM=;
 b=riEY09rkrgjK+vrfNIw4fzINyI3xM9EAepJSFxU0B1YlGYmM5MMZd+s8OhOveV3Vqr
 mdSyN2/mR+vKM6cJM5iNdgGLiWweXuW56cWSRKtngT4Jk3qPfZLOzM5C5FzvTnmmjH+l
 XQoy188FHtKfchKE4VOa2Wuz9ZGsh/zHUQCFhJttpmf19NgQSFEFbFTTaoPSBWn2D3cc
 IMnVleIS+Ym/ci4aJhMvBQ557+tyiRhJyYDhBdGD3UoJBmVeAYmc+OInJSGD++vXGq46
 kAuPPV2JhpYRh9bCBqiuRpzdG40s/EgEMyxOuMzDOrwnlLfmtnaKhQy/Ii/4VHx2KACC
 WlRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:message-id:date:mime-version:user-agent:subject
 :content-language:to:references:from:in-reply-to;
 bh=AgxyHPZj2rmpF42w7ta8fWoHOf6FCAdTgeFY5CKavtM=;
 b=3ewWo5r1TouHqea+quA5j7WqtiR9KiTen1ui4TgoOkD7MRbKv3OXiiq+4bOgbSqbiw
 kGKVoA70gD80r7xovoZTxn8kKujgUAulI4ADzL+3X6InA0buaw/VnVZ58UwnDYEyNQZg
 InL+vihq8EZqxXF7FSojQ2qyYpjaCptz1nhGP+gr6OZzc3yUmMjIMc9q2JL72B/5sBl4
 n7OvYc0dBXQ2HkLc/Jtcyeoe/EHvGLXEjeezRLEy6n0sfooKWDrdZ7ND5xlR6n8m1+u0
 BEv4GbFCuvDkEQXvbkw5B73woXZBJfz1mvgZPwWRmHFkxe6POkGgsAoYLvYji4N7035l
 6JOg==
X-Gm-Message-State: AOAM531EineYiU6XMsJ9+XAF3QdZB1uP2Dq13ezNvLTa0cJCjVZHxc0+
 r0OtYJ9v4kaD6EeY9tyHoCUADlyIKEEAJw==
X-Google-Smtp-Source: ABdhPJxIIAArIGmJOruNEXGLkpCiKkSoOthz2Q8nLNr41zjpM+KERd0BEttFsKuhqs9f9sgeAp1zzQ==
X-Received: by 2002:a5d:4523:0:b0:207:a6fc:32eb with SMTP id
 j3-20020a5d4523000000b00207a6fc32ebmr12538161wra.275.1650384477119; 
 Tue, 19 Apr 2022 09:07:57 -0700 (PDT)
Received: from [172.29.37.190] (249.red-213-96-132.staticip.rima-tde.net.
 [213.96.132.249]) by smtp.gmail.com with ESMTPSA id
 u5-20020a5d6ac5000000b00207e90b2869sm12988313wrw.91.2022.04.19.09.07.56
 for <pve-user@lists.proxmox.com>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Tue, 19 Apr 2022 09:07:56 -0700 (PDT)
Message-ID: <415781fa-8e6a-b809-cf49-5a585ffef87a@binovo.es>
Date: Tue, 19 Apr 2022 18:07:55 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.7.0
Subject: Re: [PVE-User] PowerEdge R440 & watchdog timer
Content-Language: es-CO
To: pve-user@lists.proxmox.com
References: <d22938b2-3656-3e7f-b2b7-845f2aaf6056@t8.ru>
 <mailman.275.1650032197.377.pve-user@lists.proxmox.com>
 <mailman.276.1650032585.377.pve-user@lists.proxmox.com>
 <746cb313-1ee4-8481-6904-a261634202e9@t8.ru>
 <20220415165642.0e5b20cb@sleipner.datanom.net>
 <cd411741-224a-3b0e-7aa0-7415146bfcd9@t8.ru>
 <mailman.279.1650038462.377.pve-user@lists.proxmox.com>
 <mailman.280.1650038722.377.pve-user@lists.proxmox.com>
 <mailman.337.1650380088.377.pve-user@lists.proxmox.com>
 <mailman.340.1650381816.377.pve-user@lists.proxmox.com>
From: Eneko Lacunza <elacunza@binovo.es>
In-Reply-To: <mailman.340.1650381816.377.pve-user@lists.proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 1.685 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 HTML_MESSAGE            0.001 HTML included in message
 NICE_REPLY_A           -3.247 Looks like a legit reply (A)
 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; format=flowed
Content-Transfer-Encoding: 8bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
X-List-Received-Date: Tue, 19 Apr 2022 16:08:04 -0000

Hi Michael,

El 19/4/22 a las 17:23, Michael Rasmussen via pve-user escribió:
>> So far it has worked well. Unfortunately, we haven't been able to
>> find a common pattern/cause in several clusters we see the issue.
>>
> If your corosync network is very busy and/or you have not configured
> several connections on corosync between your nodes you can try to
> increase the token value. Find the section called totem and change the
> value for token - default i 1000 (ms). I have changed the value to 5000
> I have not experienced issues since.

Thanks, didn't know this, will try it!

Regards

Eneko Lacunza
Zuzendari teknikoa | Director técnico
Binovo IT Human Project

Tel. +34 943 569 206 |https://www.binovo.es
Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun

https://www.youtube.com/user/CANALBINOVO
https://www.linkedin.com/company/37269706/