Forum Discussion

sahil_shine's avatar
16 years ago

LVM Backups

Hi All ,

We are backing up a linux client on which we have lvm and we have two filesystem /t1 and /t2  but when i start backup then backups are keep failing and i am getting ther in bpbkar in client side logs.I can see the backup is starting but some problem in reading  the file .


12:25:12.993 [23645] <4> bpbkar: INF - BACKUP START
12:25:12.993 [23645] <4> bpbkar: INF - Estimate:-1 -1
12:25:13.001 [23645] <2> bpbkar add_to_filelist: starting sizeof(filelistrec) <6
8>
12:25:13.001 [23645] <4> bpbkar: INF - Processing /t1/backups
12:40:49.981 [23645] <16> bpbkar: ERR - Cannot write to STDOUT. Errno = 110: Con
nection timed out
12:40:49.981 [23645] <16> bpbkar: ERR - bpbkar FATAL exit status = 24: socket wr
ite failed
12:40:49.981 [23645] <4> bpbkar: INF - EXIT STATUS 24: socket write failed
12:40:49.981 [23645] <4> bpbkar: INF - setenv FINISHED=0

But  earlier the problem was that the backup would happen but it will only backup folders t1 and t2 .But data under these filesystem was not backuped.Please advice.

Thanks
 -------

6 Replies

  • Have You checked if the file system created on this LVM is supported by NBU??
    For NBU 6.5. here are the supported file systems:
    OS Platform File System ACL Extended Attributes or Named Data Streams Notes
    Red Hat Ext 2/3 Yes Yes RHEL 4 kernal and later for x86, x64, IA-64. Initial support with NetBackup 6.5
    Red Hat VxFS Yes Yes (VxFS 5.0 +) VxFS 5.0 is x64 only on Linux. Initial support with NetBackup 6.5
    SUSE SLES Ext 2/3 Yes Yes SLES 9 kernal and later for x86, x64, IA-64. Initial support with NetBackup 6.5
    SUSE SLES Reiser, XFS, NSS Yes Yes SLES 9 kernal and later for x86, x64, IA-64. Initial support with NetBackup 6.5
    SUSE SLES VxFS Yes Yes (VxFS 5.0 +) VxFS 5.0 is x64 only on Linux. Initial support with NetBackup 6.5

    Taken from ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/325328.pdf

  • we are using netbackup 6.5  Enterprise server and the client is Linux 2.6.9-42.0.0.0.1.ELhugemem .. Does netbakup doesnot support these ?
  • In the mentioned PDF in my prev post there is a list of all supported clients, isn't it?
    Check You LINUX release and vendor against that list and for sure You will find out.
    I would search in /etc for file having in name release or something similar i.e. of command
    find /etc -name "*rel*" -exec cat {} \;

  • There are some network issue and server is low in memory and cpu .But i took backup at night when there is no actitivity.I had a backup for the first time but it backuped up only folders


    Policy Hardware/OS Report

    cat /etc/redhat-release
    Enterprise Linux Enterprise Linux AS release 4 (October Update 4)

    bpcoverage -derp-B output

    -------------------------

    Key: * - Policy is not active
    CLIENT - hostname (uname information)
    VERSION - NetBackup version running on the client


    CLIENT: derp-B (i686/Linux 2.6.9-42.0.0.0.1.ELhugemem #1 SMP Sun Oct 15 14:06:18 PDT 2006)
    VERSION: NetBackup-RedHat2.6 6.5.3



    bperror -client derp-B

    root@pbh04backupsrv # bperror -client derp-B
    1243531201 1 4 4 pbh04backupsrv-B 3137 3137 0 derp-B nbjm started backup job for client derp-B, policy Derp_DB_BKP, schedule full on storage unit pbh04backupsrv-B-hcart-robot-tld-0
    1243531259 1 388 4 pbh04backupsrv-B 3137 3137 0 derp-B bptm begin writing backup id derp-B_1243531201, copy 1, fragment 1, to media id TIK029 on drive HP.ULTRIUM4-SCSI.001 (index 1)
    1243531559 1 4 16 pbh04backupsrv-B 3137 3137 0 derp-B bpbrm socket read failed: errno = 62 - Timer expired
    1243531561 1 4 16 pbh04backupsrv-B 3137 3137 0 derp-B bptm media manager terminated by parent process
    1243531885 1 4 16 pbh04backupsrv-B 3137 3137 0 derp-B bpbrm timed out trying to connect to derp-B
    1243531885 1 68 4 pbh04backupsrv-B 3137 3137 0 derp-B nbpem CLIENT derp-B POLICY Derp_DB_BKP SCHED full EXIT STATUS 13 (file read failed)
    1243531885 1 4 16 pbh04backupsrv-B 3137 3137 0 derp-B nbpem backup of client derp-B exited with status 13 (file read failed)
    1243532486 1 4 4 pbh04backupsrv-B 3137 3137 0 derp-B nbjm started backup job for client derp-B, policy Derp_DB_BKP, schedule full on storage unit pbh04backupsrv-B-hcart-robot-tld-0
    1243532789 1 2 16 pbh04backupsrv-B 3137 3137 0 derp-B bpbrm cannot connect to derp-B, Operation now in progress (150)
    1243532789 1 68 4 pbh04backupsrv-B 3137 3137 0 derp-B nbpem CLIENT derp-B POLICY Derp_DB_BKP SCHED full EXIT STATUS 58 (can't connect to client)
    1243532789 1 4 16 pbh04backupsrv-B 3137 3137 0 derp-B nbpem backup of client derp-B exited with status 58 (can't connect to client)
    1243536184 1 4 4 pbh04backupsrv-B 3142 3142 0 derp-B nbpem job with jobid=3137 restarted as jobid=3142
    1243536185 1 4 4 pbh04backupsrv-B 3142 3142 0 derp-B nbjm started backup job for client derp-B, policy Derp_DB_BKP, schedule full on storage unit pbh04backupsrv-B-hcart-robot-tld-0
    1243536488 1 2 16 pbh04backupsrv-B 3142 3142 0 derp-B bpbrm cannot connect to derp-B, Operation now in progress (150)
    1243536488 1 68 4 pbh04backupsrv-B 3142 3142 0 derp-B nbpem CLIENT derp-B POLICY Derp_DB_BKP SCHED full EXIT STATUS 58 (can't connect to client)
    1243536488 1 4 16 pbh04backupsrv-B 3142 3142 0 derp-B nbpem backup of client derp-B exited with status 58 (can't connect to client)
    1243538131 1 4 4 pbh04backupsrv-B 3144 3144 0 derp-B nbpem job with jobid=3142 restarted as jobid=3144
    1243538132 1 4 4 pbh04backupsrv-B 3144 3144 0 derp-B nbjm started backup job for client derp-B, policy Derp_DB_BKP, schedule full on storage unit pbh04backupsrv-B-hcart-robot-tld-0
    1243538190 1 388 4 pbh04backupsrv-B 3144 3144 0 derp-B bptm begin writing backup id derp-B_1243538132, copy 1, fragment 1, to media id TIK029 on drive HP.ULTRIUM4-SCSI.001 (index 1)
    1243538490 1 4 16 pbh04backupsrv-B 3144 3144 0 derp-B bpbrm socket read failed: errno = 62 - Timer expired
    1243538493 1 4 16 pbh04backupsrv-B 3144 3144 0 derp-B bptm media manager terminated by parent process
  • by creating bpbkar direcotry under /usr/openv/netbackup/logs on client
    in bp.conf file on client put a line VERBOSE = 5
    restart job and paste these logs here
  • [root@derp log]# ethtool eth6
    Settings for eth6:
    Supported ports: [ TP MII ]
    Supported link modes: 10baseT/Full
    100baseT/Full
    1000baseT/Full
    Supports auto-negotiation: Yes
    Advertised link modes: 10baseT/Full
    100baseT/Full
    1000baseT/Full
    Advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: MII
    PHYAD: 11
    Transceiver: internal
    Auto-negotiation: on
    Current message level: 0x000000ff (255)
    Link detected: yes