1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

backup netapp NDMP node with TSM...failure

Discussion in 'Backup / Archive Discussion' started by combato, Apr 24, 2012.

  1. combato

    combato New Member

    Joined:
    Mar 22, 2012
    Messages:
    54
    Likes Received:
    0
    Occupation:
    A reliable employee
    Location:
    Sweden
    TSM rel. 6.2.2

    Pro’s,

    I try to backup a part of a netapp (nearstore) volume with TSM NDMP. The volume is 6 TB and the actual data size of the volume is 700 GB. The problem I have is that the backup process now have backed up over 10 TB of data. How can this be possible?
    If I check the volumes that TSM have used so far, there are no qontent on the volumes. Does anyone know how NDMP backup from a netapp works and shall be setup? Below you can see how I’ve setup my site…

    SETUP OF NDMP DUMP:
    tsm: CORPBCK4250>q node t=nas

    Node Name Platform Policy Domain Days Since Days Since Locked?
    Name Last Acce- Password
    ss Set
    ------------------------- -------- -------------- ---------- ---------- -------
    STORRY.XXX.XXXX.XX NetApp NDMP 4 11 No

    tsm: CORPBCK4250>q datamover

    Data Mover Name Data Mover Type On-Line
    ------------------------------- --------------- -------
    STORRY.XXX.XXXX.XX NAS Yes

    tsm: CORPBCK4250>q vitualfs
    ANR2000E Unknown command - QUERY VITUALFS.
    ANS8001I Return code 2.

    tsm: CORPBCK4250>q virtualfs

    Node Name Virtual Filespace Filespace Path Hexadecimal Path?
    Mapping Name Name
    --------------- --------------------- ----------- ------------------------- -----------
    STORRY.XXX.XXXX.XX /orabackup /vol/storry_sbd_vol1 /.snapshot/orabackup_kvart No

    START OF THE NDMP BACKUP:
    tsm: CORPBCK4250>Backup node storry.xxx.xxxx.xx /orabackup mgmt=sbd_10_years toc=yes mode=full

    AFTER 5 DAYS OF BACKUP:
    tsm: CORPBCK4250>q pr

    Process Process Description Status
    Number
    -------- -------------------- -------------------------------------------------
    11 Backup NAS (full) NAS Node STORRY.XX.XXXX.XX, Source /orabackup,
    Bytes Moved 10,052,066,314,240, Estimated 99%
    Completed with Data Movement, Estimated 0%
    Completed with table of contents Creation,
    Elapsed Time 316494 seconds. Current output
    volume(s): 000688L4.
    51 Backup Storage Pool Primary Pool TAPEPOOL, Copy Pool TAPECOPY, Files
    Backed Up: 231, Bytes Backed Up:
    561,836,968,387, Unreadable Files: 0, Unreadable
    Bytes: 0. Current Physical File (bytes):
    10,486,779,191 Current input volume: 000748L4.
    Current output volume(s): 000730L4.

    tsm: CORPBCK4250>q vol stg=sbdtapepool

    Volume Name Storage Device Estimated Pct Volume
    Pool Name Class Name Capacity Util Status
    ------------------------ ----------- ---------- --------- ----- --------
    000572L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000675L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000681L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000688L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000698L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000710L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000733L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000740L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty
    000762L4 SBDTAPEPOOL LTOCLASS 0.0 M 0.0 Empty

    tsm: CORPBCK4250>q cont 000572L4
    ANR2034E QUERY CONTENT: No match found using this criteria.
    ANS8001I Return code 11.

    BELOW, STAT TO VIEW THAT THE NETAPP VOLUME IS 6 TB :
    storry*> vol size storry_sbd_vol1
    vol size: Flexible volume 'storry_sbd_vol1' has size 6t.
    storry*>

    /C
     
  2.  
  3. Harry_Redl

    Harry_Redl Moderator

    Joined:
    Dec 29, 2003
    Messages:
    2,255
    Likes Received:
    134
    Occupation:
    IT Consultant
    Location:
    Czech Republic
    Hi,

    show us (from NetApp)
    df -h storry_sbd_vol1
    df -sh storry_sbd_vol1

    Harry
     
  4. combato

    combato New Member

    Joined:
    Mar 22, 2012
    Messages:
    54
    Likes Received:
    0
    Occupation:
    A reliable employee
    Location:
    Sweden
    Hi,

    Somehow... the volume I ran the backup command on has increased dramatically since I started the backup. I think I was little bit to quick to post this question...

    But I have one remaining question:
    Why can't I see any data when I type "q cont VOLNAME" ? Does the backup need to finish before I se the data on the allocated tapes?

    Output from my netapp:

    storry*> df -h storry_sbd_vol1
    Filesystem total used avail capacity Mounted on
    /vol/storry_sbd_vol1/ 6144GB 4805GB 1338GB 78% /vol/storry_sbd_vol1/
    /vol/storry_sbd_vol1/.snapshot 0GB 483GB 0GB ---% /vol/storry_sbd_vol1/.snapshot
    storry*> df -sh storry_sbd_vol1
    Filesystem used saved %saved
    /vol/storry_sbd_vol1/ 4805GB 7191GB 60%

    /C
     
  5. Harry_Redl

    Harry_Redl Moderator

    Joined:
    Dec 29, 2003
    Messages:
    2,255
    Likes Received:
    134
    Occupation:
    IT Consultant
    Location:
    Czech Republic
    Hi,

    from the output you provided it is obvious - you are using deduplication, so the volume is 6TB in size, but contains 4805+7191=11996GB.
    Yes, backup of the given object (in any backup/archive mode) must be completed before it appears in "q content".

    Harry
     
    Last edited: Apr 25, 2012
  6. inestler

    inestler Member

    Joined:
    Mar 12, 2007
    Messages:
    151
    Likes Received:
    7
    Location:
    switzerland
    In a case of a complete restore you have to have a 12TB+ volume available.
     
  7. thiago2d

    thiago2d New Member

    Joined:
    Apr 6, 2010
    Messages:
    10
    Likes Received:
    0
    friend,

    The first is FULL NDMP backup, the total size allocated on the server, not used. If you have only 6 TB allocated it will not do 10 TB backup, use the command "q fi storry.xxx / orabackup" to know the actual size allocated.
     

Share This Page