Re: [BackupPC-users] out of disk space - big oops
probably not useful to the OP at this point, but for the archives' sake i'm replying to an old thread here - Another option would be to copy your filesystem to a new raw device that is bigger (use dd to do the copy). This filesystem might in fact be an LVM device, to make this process easier next time ;) Then, use your filesystem's tools to expand the filesystem size. Most but likely not all filesystems nowadays have this capability. You'd need to do that in the LVM case too. On Thu, Feb 15, 2007 at 07:12:48AM +1000, Troy Piggins wrote: * Les Mikesell is quoted my replies are inline below : Troy Piggins wrote: By default my backuppc is backing up to /var/lib/backuppc/pc/localhost for example. I back up only 2 machines - localhost (Ubuntu linux) via tar and a WindowsXP via smb. All was going well until I added some dirs from the Windows machine, the backup jumped to about 40Gb and has filled the disk. I only have 1.5Mb free space on drive /var is mounted on. Unless you've done this before, you have no idea how hard it is to do things with no spare space. As I type this I am 'cp -a /var/lib/backuppc/pc/windows /mnt/hda4' to get windows off to another partition. Then I'll 'sudo rm -rf /var/lib/backuppc/pc/windows' to free the space. My questions: - is there a better way to migrate in future? - is there a way to tell backuppc to store backups somewhere else? or should I just mount another partition to /var/lib/backuppc/pc or similar? Any recommendations? The pool/cpool directory and the pc directory must be on the same filesystem in order for the hardlinks to work. The only way you can add Aah, I'd been reading about the hardlinks and wasn't sure to what extent they were relevant. As I said, I moved the .../pc dir, but didn't move the .../pool or .../cpool dirs. extra drives is if you are using LVM or a similar system that allows mapping multiple drives underneath a single filesystem that can grow, and then any single drive failure will lose data. I'd recommend copying what you have in /var/lib/backuppc to a much larger drive or raid (which may take a long time to reconstruct the hardlinks), then mount it or symlink the mount point into /var/lib/backuppc. Or keep what you have for emergencies and start over with a new setup on a larger drive. Depending on how much you need those old backups and how long it will take to get new runs, they may not be worth the time it takes to copy them. I think I'll do the latter - add new drive and start again. Thanks. -- Troy Piggins ,-O (o-O All your sigs are belong to us. http://piggo.com/~troy O ) //\ O RLU#415538 `-O V_/_ OOO hackerkey://v3sw5HPUhw5ln4pr6OSck1ma9u6LwXm5l6Di2e6t5MGSRb8OTen4g7OPa3Xs7MIr8p7 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/ danno -- Dan Pritts, System Administrator Internet2 office: +1-734-352-4953 | mobile: +1-734-834-7224 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] out of disk space - big oops
My suggestion, in the future, would be to consider creating the partition under Linux Logical Volume Manager (LVM). What LVM does is to create a pool of small chunks of the hard drive (extents) that can be added and removed from a given filesystem. In the case of additions, in many cases (such as with ReiserFS), this can be done on the fly. For instance, in my case. my backup partition is /var/lib/backuppc, the physical (LVM) partition is /dev/vg00/backup. For me to extend the partition by 40GB would require the following two commands: lvextend -L+40G /dev/vg00/backup resize_reiserfs /dev/vg00/backup Since the partition doesn't have to be unmounted, activity on the partition is not affected by these commands. I have a PVR on my workstation, and was recording a movie once, and had to extend the partition. It did not affect recording. HTH, --b - Original Message - From: Troy Piggins [EMAIL PROTECTED] To: BackupPC List backuppc-users@lists.sourceforge.net Sent: Wednesday, February 14, 2007 7:37:38 AM GMT-0500 US/Eastern Subject: [BackupPC-users] out of disk space - big oops By default my backuppc is backing up to /var/lib/backuppc/pc/localhost for example. I back up only 2 machines - localhost (Ubuntu linux) via tar and a WindowsXP via smb. All was going well until I added some dirs from the Windows machine, the backup jumped to about 40Gb and has filled the disk. I only have 1.5Mb free space on drive /var is mounted on. Unless you've done this before, you have no idea how hard it is to do things with no spare space. As I type this I am 'cp -a /var/lib/backuppc/pc/windows /mnt/hda4' to get windows off to another partition. Then I'll 'sudo rm -rf /var/lib/backuppc/pc/windows' to free the space. My questions: - is there a better way to migrate in future? - is there a way to tell backuppc to store backups somewhere else? or should I just mount another partition to /var/lib/backuppc/pc or similar? Any recommendations? -- Troy Piggins ,-O (o-O All your sigs are belong to us. http://piggo.com/~troy O ) //\ O RLU#415538 `-O V_/_ OOO hackerkey://v3sw5HPUhw5ln4pr6OSck1ma9u6LwXm5l6Di2e6t5MGSRb8OTen4g7OPa3Xs7MIr8p7 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] out of disk space - big oops
Troy Piggins wrote: By default my backuppc is backing up to /var/lib/backuppc/pc/localhost for example. I back up only 2 machines - localhost (Ubuntu linux) via tar and a WindowsXP via smb. All was going well until I added some dirs from the Windows machine, the backup jumped to about 40Gb and has filled the disk. I only have 1.5Mb free space on drive /var is mounted on. Unless you've done this before, you have no idea how hard it is to do things with no spare space. As I type this I am 'cp -a /var/lib/backuppc/pc/windows /mnt/hda4' to get windows off to another partition. Then I'll 'sudo rm -rf /var/lib/backuppc/pc/windows' to free the space. My questions: - is there a better way to migrate in future? - is there a way to tell backuppc to store backups somewhere else? or should I just mount another partition to /var/lib/backuppc/pc or similar? Any recommendations? The pool/cpool directory and the pc directory must be on the same filesystem in order for the hardlinks to work. The only way you can add extra drives is if you are using LVM or a similar system that allows mapping multiple drives underneath a single filesystem that can grow, and then any single drive failure will lose data. I'd recommend copying what you have in /var/lib/backuppc to a much larger drive or raid (which may take a long time to reconstruct the hardlinks), then mount it or symlink the mount point into /var/lib/backuppc. Or keep what you have for emergencies and start over with a new setup on a larger drive. Depending on how much you need those old backups and how long it will take to get new runs, they may not be worth the time it takes to copy them. -- Les Mikesell [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
Re: [BackupPC-users] out of disk space - big oops
* Les Mikesell is quoted my replies are inline below : Troy Piggins wrote: By default my backuppc is backing up to /var/lib/backuppc/pc/localhost for example. I back up only 2 machines - localhost (Ubuntu linux) via tar and a WindowsXP via smb. All was going well until I added some dirs from the Windows machine, the backup jumped to about 40Gb and has filled the disk. I only have 1.5Mb free space on drive /var is mounted on. Unless you've done this before, you have no idea how hard it is to do things with no spare space. As I type this I am 'cp -a /var/lib/backuppc/pc/windows /mnt/hda4' to get windows off to another partition. Then I'll 'sudo rm -rf /var/lib/backuppc/pc/windows' to free the space. My questions: - is there a better way to migrate in future? - is there a way to tell backuppc to store backups somewhere else? or should I just mount another partition to /var/lib/backuppc/pc or similar? Any recommendations? The pool/cpool directory and the pc directory must be on the same filesystem in order for the hardlinks to work. The only way you can add Aah, I'd been reading about the hardlinks and wasn't sure to what extent they were relevant. As I said, I moved the .../pc dir, but didn't move the .../pool or .../cpool dirs. extra drives is if you are using LVM or a similar system that allows mapping multiple drives underneath a single filesystem that can grow, and then any single drive failure will lose data. I'd recommend copying what you have in /var/lib/backuppc to a much larger drive or raid (which may take a long time to reconstruct the hardlinks), then mount it or symlink the mount point into /var/lib/backuppc. Or keep what you have for emergencies and start over with a new setup on a larger drive. Depending on how much you need those old backups and how long it will take to get new runs, they may not be worth the time it takes to copy them. I think I'll do the latter - add new drive and start again. Thanks. -- Troy Piggins ,-O (o-O All your sigs are belong to us. http://piggo.com/~troy O ) //\ O RLU#415538 `-O V_/_ OOO hackerkey://v3sw5HPUhw5ln4pr6OSck1ma9u6LwXm5l6Di2e6t5MGSRb8OTen4g7OPa3Xs7MIr8p7 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
