Search results

vm/1247 at same Task also longer than 2h to sync but would not break the Task: ... 2022-06-12T08:37:24+03:00: re-sync snapshot vm/1247/2022-06-05T21:19:02Z 2022-06-12T08:37:24+03:00: no data changes 2022-06-12T08:37:24+03:00: re-sync snapshot vm/1247/2022-06-05T21:19:02Z done...

2022-06-13T03:24:17+03:00: sync snapshot vm/1248/2022-06-12T21:29:35Z done 2022-06-13T03:24:17+03:00: percentage done: 83.75% (67/80 groups) 2022-06-13T03:24:17+03:00: delete vanished snapshot vm/1248/2022-05-31T21:42:18Z 2022-06-13T03:24:17+03:00: delete vanished snapshot...

Similar error. But after 45 hours of synchronization. 2022-06-11T09:15:00+03:00: Starting datastore sync job 'vs:hot:rmt::vs-hot' ... 2022-06-13T06:23:40+03:00: sync group vm/1249 failed - permission check failed. 2022-06-13T06:23:43+03:00: sync group vm/1250 failed - authentication failed -...

Example: proxmox-backup-manager datastore create test /mnt/data/test result: Result: "UPID:pbs:00000ADB:0AF7AAFF:00000000:60D38456:create-datastore:test:root@pam:" In this case, the /mnt/data/test directory is created. Sometimes an /mnt/data/test/.chunks directory is also created. But inside...

Thanks! Problem is solved! I need to create two files: /etc/pve/priv/bckp.cred /etc/pve/priv/storage/bckp.pw and after pvesm add cifs worked.

I tried to configure Proxmox to mount the CIFS share for ISO images and backups. For example, the repository is: bckp, the server: 192.168.1.100, user: backuper I use the cli: /usr/sbin/pvesm add cifs bckp --path /mnt/pve/bckp --server 192.168.1.100 --share bckp --maxfiles 365 --content...

No. Containers stored on local storages. NFS used only for hosting templates and backups. I will test with async. Nothing with LVM-Thinout local storage. With ZFS local storage: NAME PROPERTY VALUE SOURCE rpool sync standard local rpool/ROOT sync standard inherited from rpool...

My LXC killed every night with backup shedule. I have multiple nodes with different local storages: ZFS and LVM-Thin. All vzdump with snapshot option. All LVM-Thin have enough free space on vg volumes. And not all nodes have problem with killed LXC. All dumps created on NFS storage. Now I...

I have same problem.

Unfortunately I'm not found speed limit options at 'pct restore'. Other running VM's feel very slow perfomance with big restored dump. vzdump and rsync are equipped with --bwlimit <speed>. Howto limit 'pct restore'?

pct restore exit with error without -mpX advanced options: mounting container failed Logical volume "vm-101-disk-1" successfully removed directory '/mnt/xxx/binds/101/home' does not exist But I found solution. Just run 'pct set' on source node with new paths before 'vzdump'. And 'pct restore'...

I have some Proxmox 4.2 nodes with different hardware configuration. Nodes are not in the clusters, but have common NFS storage for backup and migration. Of course, migration without cluster downtime is inevitable. For migration from node A to node B: nodeA:/# pct shutdown $VM nodeA:/# vzdump...

Other simple solution: ssh root@192.168.1.2 'echo "echo "Europe/Paris" > /etc/timezone" | pct enter 101'