[rear-users] WG: make rescue image without backup; backup excludes

Gratien D'haese gratien.dhaese at it3.be
Wed Mar 25 09:18:48 CET 2015



A workaround for the /tmp file system which is too small is defining
a variable TMPDIR=/bigfs (with lots of spaces). This variable was
introduced for duplicity which really needs lots of temp space... 

By
the way: good work with NSR DR. Does the same trick work for NSR client
systems? Otherwise, we could add it to the default.conf file...


regards,
Gratien  

On Tue, 24 Mar 2015 20:02:22 +0100, Schlomo
Schapiro  wrote:  

Hi Dieter, 

great finding! Could you maybe
contribute us a patch that refines the "copy /nsr to rescue image" part
to actually only take the software components? That would probably help
everybody who uses ReaR with NSR. And it should not hurt using ReaR on a
backup client. 

Kind Regards, 
Schlomo 
also from Berlin :-)  

On 24
March 2015 at 18:36,  wrote:
 Hi @ all,
 my problem is solved.

 Cause:

My problem has occurred on a Networker server.
 On a Networker server,
rear tries to pack the complete Networker server filesystem into the ISO
image,
 because the mountpoint /nsr is the same as that of the Networker
client.

 Background: with BACKUP=NSR in the site.conf or local.conf,
rear tries to put the Networker client software from /nsr into the ISO
image.
 As the Networker server is also installed under /nsr, rear saves
too much data.

 Solution:
 On a Networker server, you have to exclude
the nsr server specific directories from being copied tot he ISO image:

Put this into site.conf or local.conf:
 COPY_AS_IS_EXCLUDE_NSR=(
"$NSR_ROOT_DIR/logs/*" "$NSR_ROOT_DIR/debug/*" "$NSR_ROOT_DIR/index/*"
"$NSR_ROOT_DIR/lockbox/*" "$NSR_ROOT_DIR/mm/*"
"$NSR_ROOT_DIR/repository/*" "$NSR_ROOT_DIR/scripts/*"
"$NSR_ROOT_DIR/utils/*")

 Apart from Networker servers, mkrescue or
mkbackup may also fail if the /tmp filesystem is too small,
 Here, Dirk
Reuper's workaround of redirecting the OUTPUT_DIR to another filesystem
can be the solution.

 Kind regards,
 Dieter from Berlin


-----Ursprüngliche Nachricht-----
 Von:
rear-users-bounces at lists.relax-and-recover.org [2]
[mailto:rear-users-bounces at lists.relax-and-recover.org [3]] Im Auftrag
von Michaelis, Dieter (ZIVIT Berlin)
 Gesendet: Dienstag, 24. März 2015
11:32
 An: rear-users at lists.relax-and-recover.org [4]
 Betreff:
[rear-users] make rescue image without backup; backup excludes

 Hello,

I have started using rear 1.16.1 on SLES 11 and Legato Networker Client
8.0.

 On some machines with very large file systems, rear -mkbackup
fails because /tmp is not big enogh for creating the rear backup files.

On some machines, also the manual Networker backup started by rear
fails.
 I would prefer to create a rescue image (root partition +
Networker client) only - the Networker recovery can be done later by the
backup team.

 How can I
 -restrict the rear backup to create a rescue
image only -exclude large file systems from the backup

 I have tried

-rear mkrescue
 -"EXCLUDE_BACKUP=('/bigfs/*')" in site.conf
-"EXCLUDE_BACKUP_PRG=('/bigfs/*')" in site.conf
-"EXCLUDE_MOUNTPOINTS=('/bigfs')" in site.conf But it does not work.

Rear always starts creating backup files in /tmp from all mounted
filesystems and the disk runs full.
 Any help would be appreciated!


Kind regards, Dieter

 _______________________________________________

rear-users mailing list
rear-users at lists.relax-and-recover.org
[5]
http://pikachu.3ti.be/mailman/listinfo/rear-users [6]

_______________________________________________
 rear-users mailing
list
rear-users at lists.relax-and-recover.org
[7]
http://pikachu.3ti.be/mailman/listinfo/rear-users [8]

-- 

Gratien
D'haese
IT3 Consultants bvba 
Vennestraat 15, B-2560 Nijlen



Links:
------
[1] mailto:Dieter.Michaelis at zivit.de
[2]
mailto:rear-users-bounces at lists.relax-and-recover.org
[3]
mailto:rear-users-bounces at lists.relax-and-recover.org
[4]
mailto:rear-users at lists.relax-and-recover.org
[5]
mailto:rear-users at lists.relax-and-recover.org
[6]
http://pikachu.3ti.be/mailman/listinfo/rear-users
[7]
mailto:rear-users at lists.relax-and-recover.org
[8]
http://pikachu.3ti.be/mailman/listinfo/rear-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pikachu.3ti.be/pipermail/rear-users/attachments/20150325/32a3581c/attachment-0001.html>


More information about the rear-users mailing list