Over the years, many have asked and struggled with backing up remote
Windows shares with shadow copies. Shadow copies are useful since they
allow both the backup to be 'consistent' and allow for reading files
that are otherwise 'busy' and unreadable when part of active Windows
partitions.
Various
For what it's worth, I was able to resolve this (for now) by updating CPAN
itself. I noticed when running certain commands that it complained that CPAN
was at version 1.x and version 2.28 was available. It suggested running:
install CPAN
reload cpan
But those are clearly not bash
hi,
You think I would have run across this with all the Linux systems I
administer but I had not. You are correct systemctl stop worked.
Thank you.
Mark
> Mark,
>
> Perhaps systemd is being used to run BackupPC?
>
> What output do you get from:
>
> systemctl status backuppc
>
> If it shows as
Mark,
Perhaps systemd is being used to run BackupPC?
What output do you get from:
systemctl status backuppc
If it shows as active/running, then the correct command to stop BackupPC is:
systemctl stop backuppc
Craig
On Mon, Jun 29, 2020 at 11:05 AM Mark Maciolek wrote:
> hi,
>
> Running
hi,
Running BackupPC v4.3.2 on Ubuntu 18.04 LTS. I want to upgrade to 4.4.0
but I can't get the backuppc process to stop. I can do
/etc/init.d/backuppc and it starts again. If I do kill -9 it
also just restarts.
I have several other BackupPC servers and yet this is the only one that
does this.
I'll clarify a bit: the Backup.sock and LOCK file deletions were a long
shot that just happened to work. I noticed that those files were there with
the service stopped, and my suspicion / reasoning was that perhaps backuppc
was having trouble generating the socket because those represented a hung
G.W. Haywood via BackupPC-users wrote at about 14:16:15 +0100 on Monday, June
29, 2020:
> Hi there,
>
> On Mon, 29 Jun 2020, Craig Barratt wrote:
>
> > ...
> > Are you running nfs v3 or v4? I have had experience with v3 not working
> > reliably with BackupPC (related to buggy lock file
For what it is worth, I have been using an nfs mount to hold the pool
files for both BPC V3 and V4. This is the fstab entry:
192.168.1.80:/mnt/HD/HD_a2/POOLS /home/disks/nasPOOLS nfs nolock,rw,suid 0 0
The man page nfs(5) explains that nolock does not turn off locking
completely.
On
Hi there,
On Mon, 29 Jun 2020, Craig Barratt wrote:
...
Are you running nfs v3 or v4? I have had experience with v3 not working
reliably with BackupPC (related to buggy lock file behaviour). BackupPC
does rely on lock files working, so it's definitely not recommended to turn
locking off.
