Hi,
Richard Bailey wrote on 02.06.2007 at 11:07:09 [[BackupPC-users] Migrate backup
pool to new server]:
> Hello, I'm in the process of planning the rebuild of my home server to
> beefier hardware, which will require a reinstall of the OS.
with Windows I'd agree. With Linux: why? Even changing the hard disk *might*
be faster and easier with a 'dd' of each file system (and possibly resizing
it afterwards) and an invokation of 'lilo' or 'grub-install' or the repair
option of your favorite Debian etch DVD ;-). It all depends on how much you
want to change on the software side (new distribution (version), different
partition layout, file system types, new architecture (64 bit), general
cleanup?). Yes, there are some pitfalls like having / on an SATA hard disk
with a chipset not supported by a driver compiled into the kernel ... but if
you're happy with the software environment as it is now, it might be worth
trying to keep it rather than rebuild it.
> BackupPC backs
> up to an external disk. To test that I can move the backup repository to a
> new server I just did a test install on my desktop, plugged in and mounted
> the disk and restarted BackupPC, but there are permissions problems since
> the UID and GID are different.
Johan Ehnberg answered on 03.06.2007 at 12:06:58 [Re: [BackupPC-users] Migrate
backup pool to new server]:
>
> After copying the data files - while preserving hardlinks (important!) -
No. No need to copy anything. Simply connecting the disk to a new computer
is fine.
> you would have to run a 'chown -R backuppc:backuppc *' for all backuppc
> files,
In other words: 'chown -R backuppc:backuppc /var/lib/backuppc'.
The configuration files under /etc should already be correctly set up,
unless you replaced them with old ones with wrong ownership. In that case,
change ownership and permissions back as they were. A normal 'cp' without
'-p' (or '-a') to an existing file should leave ownership and permissions
untouched, so if that's what you did, everything should be fine.
> I am not completely sure this is all you need to do, someone advise if
> more is necessary to get the internal workings of backuppc up to date.
If you're using the same version (and distribution) of BackupPC on the new
machine, that should be all. Otherwise, you might need to move around the
configuration files. At least, nothing else springs to mind.
As an alternative approach, you can change the UID and GID of the backuppc
user (presuming the previous values are not used by another user/group)
instead of the ownership of the pool files. You will need to change ownerships
of files installed on the new system (config files, setuid web script) to
match the changes, but you'll have a pool disk that you can easily move
between the two systems. Make a note of the UID and GID used before you
change it if you do, just in case you need to fix something later. You can
find all files belonging to UID or GID with something like:
find / \( -user UID -o -group GID \) -ls
(do that without the pool disk mounted to save you some time :-).
Along the same line, you could
find / -user OLDUID -print | xargs chown NEWUID
find / -user OLDGID -print | xargs chgrp NEWGID
if you simply want to change all of them, which is not unlikely.
This would also work for the pool file system, but it's somewhat
unnecessary, as all files there should match.
Regards,
Holger
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
