Search results

  1. damon1

    not sure if it is related but had something bad happen today

    it is related on the local network there is a VM which has PBS installed. Once I "shutdown now" the VM all the grey went away.
  2. damon1

    not sure if it is related but had something bad happen today

    i have posted it on the other forum but I think the root cause might be the PBS https://forum.proxmox.com/threads/all-nodes-and-vms-have-a.77289/ thanks damon
  3. damon1

    all nodes and VM's have a ?

    this might be a bit of a worry given i am testing the PBS. This it is what might have caused my problems today. I know there was a job which was to run last night which I stopped after 17 hours. But this is still running now this is from the remote PBS server looking at the time I...
  4. damon1

    all nodes and VM's have a ?

    also ceph is totally out of whack
  5. damon1

    all nodes and VM's have a ?

    all the VM's are running. I can use a remote access to log into the VM's and the applications running on the VM's are responding. any idea how to fix it, preferably without rebooting the nodes? thanks damon
  6. damon1

    PBS remote to PBS problem with "owner check error"

    Hi Fabian, I found a work around which is to "add root@pam to the PERMISSIONS of the Datastore". It does not show anything being added to the list but you can then run the job. To confirm the first time I found this error I DID delete all the files fromt he file store so it was empty. The error...
  7. damon1

    PBS remote to PBS problem with "owner check error"

    On system A ( the doner system on the local VM network), I see the owner as however on the receiver / WAN / remote PBS I see the owner as being
  8. damon1

    PBS remote to PBS problem with "owner check error"

    Sorry guys , not sure what I did BUT i clicked around and tried to add root@pam to the PERMISSIONS of the Datastore on PBS B. it didn't seem to do anything or even save in the list but I clicked on RUN and now it is running. Sorry thanks Damon
  9. damon1

    PBS remote to PBS problem with "owner check error"

    I have a PBS setup at location A which also has all the VM's on the same network I have PBS set up at location B which is where I would like to sync the datastores from PBS A to PBS B on PBS B I have set up the remote as being PBS A Port 8007 is forwarded when it runs it returns these...
  10. damon1

    initial VM backup

    HI Dominik, thanks for the tip regarding rsync. I am sure for someone who uses Linux even semi-regularly then this would be simple. For me, and possibly other windows users, it is near impossible. if I hadn't found MC (Midnight Command) then I would not be able to navigate the linux disk...
  11. damon1

    initial VM backup

    lastly, if anyone is wondering about what memory or CPU are required this is a slow i7 with 16GB of 1666MHz DDR3 memory looks like the machine specs are not in the equation at all even with a ZFS drive. The Network or WAN bandwidth is the bottleneck as expected. thanks damon
  12. damon1

    initial VM backup

    just noticed something when trying/looking to improve the performance or to assist others. on the Proxmox nodes the back up is running, the backup now defaults to the selected but then changes to this I think this is great as the BACKUP to PROXMOX are talking to each other. Possibly get rid...
  13. damon1

    initial VM backup

    just a thought. could you upload via local media a copy of the initial VM. Similar to CLONE but CLONE to USB then take the USB to the BACKUP machine and UPLOAD the initial VM via UPLOAD etc... . On the local network it took about 10 minutes on 10GB LAN but WAN, I expect it to take a quite a...
  14. damon1

    little windows help

    if you know less about Linux try this in the BACKUP GUI (the one https:/192.168.0.xxx:8007) you click on DISKS ZFS Create ZFS you select a drive You enter a name for the drive using the standard rules - don't start with a 12345 etc. remember the name you give it will be used below - don't...
  15. damon1

    gentle warning : windows 10 version 2004 update and Proxmox

    HI Guys, gentle warning If you have Windows 10 Vm which is about to update to version 2004 you should take a snapshot now I have found that 6 of 7 update fine but the others get stuck in a endless loop between the Proxmox Bios Boot ( the screen with ESC for boot options) and then next page...
  16. damon1

    [Solved] Can't ping windows VM

    NOTE to myself incase it happens again open in windows firewall File and Printer Sharing (Echo Request - ICMPv4-In) and/or Core Networking Diagnostics - ICMP Echo Request (ICMPv4-In) the latter changed in the windows update 17 Sept 2020 - Yeah Microsoft !!!! thanks Damon
  17. damon1

    CEPH : Nice simple one's :)

    Brilliant, will look at the best / low latency SSD or HDD we can afford Thanks for the answer to #3, I will start to Google what it all means. But I appreciate I have a starting point for the next project. Many Thanks Damon
  18. damon1

    CEPH : Nice simple one's :)

    update -> an hour later HDD is still very bad during re-balance / recovery
  19. damon1

    CEPH : Nice simple one's :)

    After running CEPH for a year, I decided to replace a node as the performance was not what I expected. (Two days later, insert multiple expletives, one less keyboard and a few grey hairs) First thing - double check you have put in the right network card. -> those 2x 10GB look very similar to...
  20. damon1

    [SOLVED] Unable to install Ceph from GUI - fresh pve 6.2-11

    Update: When I look in the SYSLOG I see a lot of these? Sep 03 16:14:01 DC5 pvestatd[1751]: got timeout Sep 03 16:14:02 DC5 pvestatd[1751]: status update time (5.460 seconds) Sep 03 16:14:11 DC5 pvestatd[1751]: got timeout Sep 03 16:14:11 DC5 pvestatd[1751]: status update time (5.452 seconds)...