1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

Moving archived data from file pool to tape pool: Files skipped due to deletion?

Discussion in 'Backup / Archive Discussion' started by RecoveryOne, Sep 8, 2017.

  1. RecoveryOne

    RecoveryOne ADSM.ORG Member

    Joined:
    Mar 15, 2017
    Messages:
    57
    Likes Received:
    6
    TSM on AIX 7.1 TSM version 7.1.7.000

    Few weeks ago, had a request to archive a system for several years. Archives won't likely be accessed and can go to tape. Figured we could setup our management class for archives to send it to our deduplicated file pool and then later on issue a move nodedata type=archive to move the archive data of the node to tape. I just don't have the resources to dedicate a landing zone for archive data so thought this would work out pretty well.

    Today, after getting some time and my tape drives idle issued the move nodedata command:
    Code:
    09/08/2017 13:41:48 ANR2017I Administrator ADMIN issued command: MOVE NODEDATA <NODE> from=file_dedup_pool to=archive_pool type=archive  (SESSION: 857535)
    09/08/2017 13:41:48 ANR1649W MOVE NODEDATA:This command will move data for nodes stored in storage pool FILE_DEDUP_POOL to storage pool ARCHIVE_POOL; the data will be inaccessible to users until the         operation completes. (SESSION: 857535)
    09/08/2017 13:41:49 ANR1645I MOVE NODEDATA:  Data for node <NODE>, filespace <NODE>\SystemState\NULL\System State\SystemState, FSID 1 will be moved. (SESSION: 857535)
    09/08/2017 13:41:49 ANR1645I MOVE NODEDATA:  Data for node <NODE>, filespace ASR, FSID 2 will be moved. (SESSION: 857535)
    09/08/2017 13:41:49 ANR1645I MOVE NODEDATA:  Data for node <NODE>, filespace \\<NODE>\c$, FSID 3 will be moved. (SESSION: 857535)
    09/08/2017 13:41:49 ANR1645I MOVE NODEDATA:  Data for node <NODE>, filespace \\<NODE>\d$, FSID 4 will be moved. (SESSION: 857535)
    09/08/2017 13:41:49 ANR0984I Process 2728 for MOVE NODE DATA started in the BACKGROUND at 13:41:49. (SESSION: 857535, PROCESS: 2728)
    09/08/2017 13:41:49 ANR1284I Move node data started as process 2728. (SESSION: 857535, PROCESS: 2728)
    09/08/2017 13:41:49 ANR2110I MOVE NODEDATA started as process 2728. (SESSION: 857535, PROCESS: 2728)
    Ok looking good.
    Then it finishes:

    Code:
    09/08/2017 15:11:39 ANR3246W Process 2728 skipped 4 files on volume /TSMSTG03/FILE_DEDUP_POOL/00014B79.BFS because the files have been deleted. (SESSION: 857535, PROCESS: 2728)
    09/08/2017 15:11:39 ANR1141I Move data process ended for volume /TSMSTG03/FILE_DEDUP_POOL/00014B79.BFS. (SESSION: 857535, PROCESS: 2728)
    09/08/2017 15:11:39 ANR1288I Move node data process 2728 ended for storage pool FILE_DEDUP_POOL. (SESSION: 857535, PROCESS: 2728)
    09/08/2017 15:11:39 ANR0986I Process 2728 for MOVE NODE DATA running in the BACKGROUND processed 2,170,782 items for a total of 127,038,147,276 bytes with a completion state of SUCCESS at 15:11:39.          (SESSION: 857535, PROCESS: 2728)
    
    So 4 files skipped due to it being deleted?

    Let me see what they are. Upon the day of archiving the node in question I ran a query to document every file archived and put the results it in our internal ticket system. The query I used is:
    Code:
     select filespace_name||hl_name||ll_name as "Full name", description from archives where node_name='<NODE>'
    Reran the query today in hopes of finding out what four files were that were deleted, upon diffing the results: nothing is showing out of place, no missing files.

    I double checked the mgmtclass/archive copygroup that the archives are bound to and its retver is at 3,650.

    So, while I start up a PMR was wondering if anyone here has seen this?
     
  2.  
  3. RecoveryOne

    RecoveryOne ADSM.ORG Member

    Joined:
    Mar 15, 2017
    Messages:
    57
    Likes Received:
    6
    Just tossing an update to this:
    Turns out the messages can be safely ignored as provided by T2 support.
     

Share This Page