Search results

I get this error when trying to add a new user to PBS, version 3.2.9. What's wrong?

Ok, but I think there's an issue on that. If I have a script where I backup something, and later want to create a comment, how do I find the ID of the backup I've just done?

Ok. Please one more. If there's only one backup (i.e., done with default mode), if for the second I switch to metadata, will there be any issue, or should all be with the same? This is another way to ask if for the very first backup the data is stored regardless the mode.

I¡m still unsure on how to interpretate that for my use cases. Let's say there are 2 cases: 1) Data is about 95% or more the same (the system part), being the changing part is log files. There's an exception when an upgrade takes place. 2) Data is "added", existing files are seldom modified...

About datastore, page 29 of pdf says: How accurate is this, so other options like btrfs could work? I thought that, because of "things related to how chunks are managed", btrfs could have some incompatibility, but I'm happy if the list of supported filesystems for a datastore is open. Thanks

Thanks for your reply, but if I don't misunderstand, you mean there's no way to move, but somehow "classic" copy and delete source. Did anyone think about adding this feature to make it in a safer way, as long as this isn't implemented yet?

I'm setting up a PBS that has large storage and can manage data from several sources. This is reachable, but the source is in a VPN and I don't have intention to open security in that direction. So, the "local" PBS is storing the backups, and being the remote listening, can i sync from the local...

It happened to me that manually creating a backup, I used a wrong datastore (it could be also with a namespace). Regardless a mistake or later reorganization, is there a way to move finished (and verified) backups between datastores or namespaces?

I run the pbs in a ct, and setting up a storage in PVE, there's no problem. About the possible chicken and egg issue, as long as you don't want to replace PBS and it's somehow working, you can even have a dupiicate in shutdown state for emergency and start when necessary (I didn't test this). Of...

Hi. I'm reading the docs and am unable to find an option to store a comment via proxmox-backup-client, similar to vzdump notes in the gui. Is this possible?

Maybe I didn't explain clearly. I used btrfs as second step for temporarily storing a manual backup of the source data, once that the first temporary lv was with ext4 and showed corruptions. Then, I unmounted and repaired the failing failsystem, and mounted it back after checking. The datastore...

Well, I found the problem. The underlying fs for datastore had problems. I noticed when started verifying the jobs, and all were corrupt indicating errors in the datastore. I've repaired the fs and created a new datastore, and I'm doing them all and verifying. I hope this time it's ok.

Do you mean fsck on datastore or on where the data is stored? As I said, it's recentrly reformatted in btrfs and I've checked it. Unless you mean it can become corrupted within a short period of time with no use.

Hi. I'm using PBS to backup my data. There's a ct running a nextcloud instance, and that ct has a separate mount point for the data (~100GB). I run at os level the proxmox backup client for that directory, and found out that there are errors that I'm currently debugging. Also, take into account...

You didn't post any of your NAT settings. First, check that all routing works ok prior to being natted, including what you claim not working. Of course, check ip_forwarding is enabled. And check things that should NOT be natted, but forwarded.

In vmbr0 you set "hateway" instead of gateway.

I have exactly the same case as you, but I get the same newuidmap error. I think the /etc/subuid and /etc/subgid must have more than the root:33:1 line that I'm missing. Can you (or anybody else) post if this is wrong and the missing contents? Thanks in advance.

No luck with that method. I've tried something different. I've just assigned at the host the user 100000 and the group 102120 to the shared dir and set permissions accordingly. It's been necessary to add both full uid and gid mappings in the config file, like this: lxc.idmap: u 0 100000 65536...

Ok. I think that it's the same using 1005 than 2120, so I've done this: # grep lxc 120.conf lxc.idmap: u 2120 2120 1 lxc.idmap: g 2120 2120 1 # cat subuid root:2120:1 # cat subgid root:2120:1 But now I get this error: # lxc-start -F -n 120 lxc-start: 120: conf.c: chown_mapped_root: 2902...

Surely there's some silly concept I'm misunderstanding, but I'm unable to find out what I'm doing wrong. In my specific case, I just need to preserve host gid 2120 to the same gid in the container . Do I need to remap *all* uids and gids? What is mandatory for /etc/subuid and /etc/subgid, and...