Search results

  1. P

    2FA not supported

    Thanks for the quick reply. It worked :)
  2. P

    2FA not supported

    Hi - just installed new Datacenter manager and it looks pretty good. However, when trying to add a remote, it says it does not support 2FA, so therefore it won't accept my user and therefore I can't add the remote. Are you working on a way to link remotes that use 2FA? Thanks
  3. P

    Hidden backup jobs

    Thanks everyone for your ideas. I figured it out. Apparently the "hidden" jobs weren't hidden at all. They were coming from a test server that I use for playing with VMs before using in Production, and I had forgotten about these backups. So the good news is there aren't any problems with...
  4. P

    Hidden backup jobs

    Hi - apparently I don't have a jobs.cfg file. (see attached screenshot of /etc/pve folder)
  5. P

    Hidden backup jobs

    In a web browser that I typically don't use, and just to be sure I deleted all history/cache/everything from it first, then closed and reopened the browser and then logged into proxmox. I don't see anything different than my normal browser. On the Datacenter tab, under the new Backup tab, it...
  6. P

    Hidden backup jobs

    Hi Dunuin - I know that 6 & 7 are different, but all of my backup jobs were created in 6 before the upgrade and have been working fine for over a year. However now that I started adding / deleting some new VMs as I test various programs etc... there seems to have been a disconnect somewhere...
  7. P

    Hidden backup jobs

    Something strange happening here. I have some backup jobs running that shouldn't be and I can't find where the command is that is telling them to run. I originally setup my cluster back on Promox 6 with PBS1. (Now upgraded to 7.2.7 and PBS 2.2.5) At that time, the GUI couldn't handle all of the...
  8. P

    [SOLVED] error fetching datastores - 500 after upgrade to 2.2

    Hi Mira - I understand it's difficult to troubleshoot something that is not consistent. In continuing to research it myself I think I might have figured it out? Could it be the syntax used in the cron job? Since the start, (over a year ago) my cron file has contained the following...
  9. P

    [SOLVED] error fetching datastores - 500 after upgrade to 2.2

    nope - upgrading Proxmox to 7.2-4 didn't help. It must be some change in PBS... an initial command to activate the storage? something that changed from version 1?
  10. P

    [SOLVED] error fetching datastores - 500 after upgrade to 2.2

    no problem. Running a 3 node HA cluster that was on Proxmox 6.4, connecting to a PBS server which was on 1.something (I don't remember the exact version of 1). The PBS is running as a VM on one of the nodes. Everything has been running perfectly for over a year, until I upgraded the PBS to...
  11. P

    [SOLVED] error fetching datastores - 500 after upgrade to 2.2

    Hi dcsapak Don't know if you noticed yet or not, but several more of us seem to have this issue. Perhaps you can get the Devs to dig into it a bit more? Thanks
  12. P

    Slow garbage collection on PBS

    Hi - just curious how you created a PBS datastore on CEPH? Thanks
  13. P

    [SOLVED] error fetching datastores - 500 after upgrade to 2.2

    Adding some more info as I investigate. I just tried connecting to the datastore from commandline from cluster nodes using the "proxmox-backup-client list --repository xx.xx.xx.xx Datastore" command, and it worked (eventually) BUT it did prompt me to accept the fingerprint twice! Why the...
  14. P

    [SOLVED] error fetching datastores - 500 after upgrade to 2.2

    hello - I have same thing happening. In the process of upgrading my cluster from 6.4 to 7 series. Before doing that I upgraded my PBS server as recommended by your docs for upgrading process. The PBS server upgraded to version 2.2-3 worked fine and I can see my Datastore everywhere (in the...
  15. P

    How to create hourly backup for a proxmox vm on PBS?

    I know this has been asked for already, but just adding my vote for being able to do this through the GUI. And if directly editing the CRON job is still the way to go, then at least don't break the GUI - as soon as I edited the vzdump file, the schedule disappeared from the GUI. The sad part...