Hi,
I did mean 3 and 4. Thanks for the input, I'll try to work on it over
the next month.
Gerald
On 2016-10-27 08:26 AM, Holger Parplies wrote:
> Hi,
>
> Gerald Brandt wrote on 2016-10-25 11:43:22 -0500 [[BackupPC-users] BackupPC 4
> questions]:
>> Can I run BackupPC 4 on the same machine, and at the same time, as I'm
>> running BackupPC 4?
> obviously: yes :-).
>
> You probably meant to ask whether it is possible to run BackupPC 3 and 4
> concurrently. I can't see any reason why it shouldn't be. You will obviously
> need to choose distinct values for $TopDir, $LogDir, and $ConfDir between both
> instances (the latter two may or may not default to a value dependent on
> the first). I don't really know much about version 4, but from BackupPC 3's
> perspective, these seem to be the only resources that won't like shared write
> access. If you've defined $Conf {ServerPort}, you'll obviously need distinct
> values there, too. BackupPC 4 might name some of these settings differently
> (though I doubt it), so you might need to figure out what they correspond to.
>
> It probably goes without saying that you'll need to install to different
> paths and maybe rename an init script. This may be a problem if you're
> installing from distribution packages (in which case they should also conflict
> with one another) - supposing there even are distribution packages for
> BackupPC 4 yet.
>
> I probably don't need to mention that running BackupPC 3 and 4 concurrently
> on the same system may impose loads on the hardware that it can't handle
> (meaning backups taking too long), but that doesn't seem to be relevant in
> your case:
>
>> I'd like to do some tests, and maintain my old system at the same time,
>> without buying new hardware.
> So, try it out and tell us if you found a conflict that I missed. At least
> I can't see any obvious reason not to try, providing you choose different
> paths as mentioned above. If it makes you feel more secure, stop the BackupPC
> 3 daemon and remount your pool FS read-only for testing - at least for the
> first backup. Obviously, you'd need to store your V4 pool on a different FS
> then, but that's probably not a bad idea anyway.
>
> Of course, if you're really cautious, you could always run V4 in a VM ...
>
> #include <standard-disclaimer.h> /* or rather */
> use Disclaimer::Std; # since we're talking Perl here
>
> Hope that helps.
>
> Regards,
> Holger
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
