Hi all, We're using BackupPC in two datacenters backing up local VMs and bare metal servers and things in the opposite DC.
I've spotted a weird thing where one DC server is supposed to be backing up a host in the other DC, but it actually turns out to be backing up itself because we messed up copying the BackupPC config. For example: * BackupPC node 1 is gavin.suretec.net in DC1 * BackupPC node 2 is henry.suretec.net in DC2 Now gavin.suretec.net BackupPC server config was copied to the new server in the other DC onto henry.suretec.net henry.suretec.net server config in BackupPC says the host is gavin.suretec.net and the server URL is gavin.suretec.net when it should be henry.suretec.net really. DNS is correct in that gavin.suretec.net is in DC1, but even after changing all the BackupPC server details to henry.suretec.net, it's still treating henry.suretec.net as the other host (gavin.suretec.net), i.e. it's not connecting to gavin.suretec.net to rsync data back. It's just rsyncing to itself. I just can't figure out why it still thinks it's the other BackupPC node. There are some local database dumps done to that server I want to pull down to the other BackupPC node via normal backup jobs run via BackupPC. I'm not trying to backup BackupPC data, just a folder. I originally checked the folder that was rsyncing in case rsync saw an underlying mounted filesystem or something, but it's not that. I've restarted backuppc too. Make sense? What else can I check? I've ssh'd to the other node as the correct user and it connects as I'd expect. -- Kind Regards, Gavin Henry. _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
