can't backup /home in linux

[santave]

Hi,

Master server: Linux RHEL 6, nbu 7.5.0.6
Client : Linux RHEL 6 , nbu 7.5.0.6

Backup Policy :
Cross mount point : disabled
BMR and TIR : enabled
Multiple data stream : enabled

The full backup is failed with status 14 for /home, with below error:

Error bpbrm (pid=65073) from client host1: ERR - Cannot write to tir_info_file, fd is NULL

is the any workaround to fix this issue?

Thanks,
Santave
 

[rk1074]

check this out:

http://www.symantec.com/business/support/index?page=content&id=TECH67249

Would also like to see the output of bppllist <policy name> -U

[santave]

I have available space for this.
I read some technote that, the solution is multiple data stream need to be disabled, if BMR enabled.

Is there any other way, since I need multiple stream enabled?

[Marianne]

Please show us output of these commands on the client:

df -h

/usr/openv/netbackup/bin/bpmount

We need to know what type of filesystem /home is - NFS? autofs/automount?

[santave]

I tested this in other 3 linux servers client, all same error for /home backup.

Its ext4 local disk, pls find below details.
Any clue ?

df -h
/dev/mapper/proot_vg00-phome_lvol0005
                       40G  830M   37G   3% /home

/usr/openv/netbackup/bin/bpmount result
ext4: /dev/mapper/proot_vg00-phome_lvol0005 on /home
EXIT STATUS 0: the requested operation was successfully completed

fstab file:
/dev/mapper/proot_vg00-phome_lvol0005 /home                   ext4    defaults        1 2

[Marianne]

Please create bpbkar log folder on client. Increase logging level to something like 3.
After next failure, copy log file to bpbkar.txt and upload as File attachment.

[Nicolai]

Please consider this technote:

http://www.symantec.com/docs/TECH31513

[santave]

I used logging level 3.
PFA, the bpbkar log.

[Nicolai]

18:20:59.061 [25065] <8> bpbkar SelectFile: WRN - [/home] is on file system type PROC. Skipping

I am wondering why /home is considered as PROC. It seems the type changes a lot of times in the bpbkar log.

18:25:05.200 [25065] <2> mount build_mount_list: INF - Processing (ext4) /dev/mapper/proot_vg00-phome_lvol0005 on /home

18:25:05.201 [25065] <2> mount build_mount_list: INF - Mount options for /home are <rw,bind>

18:25:05.201 [25065] <2> mount build_mount_list: INF - Changed cur_fstype to proc for /home

18:25:05.201 [25065] <2> mount build_mount_list: INF - Processing (none) /home on /home

Update: I think it's the bind option on the filesystem. bind options make it possible to remount part of the file hierarchy somewhere else.

Some background info: 

http://lwn.net/Articles/281157/

Santave: You need to talk to the UNIX admin. 

[santave]

Nicolai,

Sorry, I dont really get what things I need to talk to Unix admin.
filesystem for /home looks like same with other at fstab.
Also, I can backup /home if BMR and TIR disabled. What diff when I enable it?

Thanks,
Santave

[Nicolai · Accepted solution]

I look like a subset of /home is not part of the /home file system but monted somewhere else using the "mount -o bind" option.

Bring the info I provided in my last post to the UNIX admin, I think he will understand the information.

One quick fix is to exclude /home from the backup and create a separate non-BMR/TIR backup of /home

[Marianne]

I am curious about the fact that /home backs up fine without BMR and TIR. Would like to see bpbkar log of successful backup to compair with the failed backup. ...

[santave]

Hi,

This is the backup log without BMR and TIR, backup completed with status 0.
But I just realised, when I browse in BAR gui, there is nothing in /home.

Why [/home] is on file system type PROC. Skipping?

Thanks,

Santave

12/13/2013 16:17:38 - Info bpbrm (pid=12799) start bpbkar on client
12/13/2013 16:17:38 - Info bpbkar (pid=38107) Backup started
12/13/2013 16:17:38 - Info bpbrm (pid=12799) Sending the file list to the client
12/13/2013 16:17:38 - Info bpbrm (pid=12987) from client osdinfsrbpapp1b: TRV - [/home] is on file system type PROC. Skipping
12/13/2013 16:17:38 - connecting
12/13/2013 16:17:38 - connected; connect time: 0:00:00
12/13/2013 16:18:19 - mounted LV5328
12/13/2013 16:18:19 - positioning LV5328 to file 173
12/13/2013 16:19:28 - positioned LV5328; position time: 0:01:09
12/13/2013 16:19:28 - begin writing
12/13/2013 16:19:32 - Info bpbrm (pid=12799) media manager for backup id osdinfsrbpapp1b_1386926257 exited with status 0: the requested operation was successfully completed
12/13/2013 16:19:33 - end writing; write time: 0:00:05
the requested operation was successfully completed  (0)
 

[Marianne]

As per Nicolai's post - PLEASE discuss this with system administrator.

PROC filesystems are automatically skipped (except on AIX).

See http://www.symantec.com/docs/TECH52350

Other (similar) discussions:

https://www-secure.symantec.com/connect/forums/skipped-files-solaris-10

https://www-secure.symantec.com/connect/forums/directory-inside-home-partition-skipped-during-backup

https://www-secure.symantec.com/connect/forums/bmr-backup-failed-1