Search results

Unter ServerAdministartion/Updates gibts einen "Changelog" button ... Natürlich findest du die changelogs auch unter /usr/share/doc/{PACKAGE_NAME}/changelog* (wie auf allen Debian Systemen)

Using local disks is usually much cheaper than those "professional SAN/s". It is also much faster. But its all up to you. The backup server is based on Debian Linux, so you can use any network storage (cifs, nfs, iscsi). You can backup the server config. We already have file level backup and...

There s a simplified syntax for the command line: # qm set 1000 --scsi1 YourVMStorageId:32 This is mentioned in the "qm" manual page:

Server "load" (https://de.wikipedia.org/wiki/Load) is kind of "artifical" messurement. I goes up because of the CPU limit (more processes waiting for the CPU). > Surely only the LXC container should have that type of load average? The host see all processes from all containers, so it shows...

We are working on that "namespace" feature...

Please can you post the output of # pveversion -v

Maybe you are on the wrong node?

You need to use a reasonable fast storage.

Bitte überprüfe ob all deine storages funktionieren: # pmesm status Oft tritt das problem auf wenn ein netzwerk storage blockiert (z.B. NFS) ...

First, our Software is licensed under APGLv3, and it is free to use (no license costs at all). Note: "Subscriptions" are support options. yes

Any hint is syslog?

Most likely a problem with the underlying storage. Do you use a qcow2 format? If so, please check if that file has errors ("qemu-img check")

All chunks are compressed, unless compression leads to bigger files. In that case we store uncompressed because that is smaller.

It is currently not possible to change that. Please can you open a bug report (feature request) at https://bugzilla.proxmox.com/ - I guess this is easy/fast to implement.

I would simply ignore that warning. The suggested setting does not really help at all.

What is the output of: # proxmox-tape changer scan And what product do we talk about exactly (LTO version)

You can setup a "remote" for localhost, then pull the contents from one store to the other. See # proxmox-backup-manager pull

Well, that username is a real mess Using 64 characters for the userid is nonsense... I suggest that you set the "username_claim" property to use another claim as username (maybe email).

Those are Non-delivery reports (NDRs) - quite normal...

Klingt nach DNS problem (SSH macht lookups auf den hostnamen). Funktioniert das DNS im container?