Tapepool Size does not match OFFSITE after backup

DMobley232

ADSM.ORG Member
Joined
Oct 20, 2016
Messages
76
Reaction score
3
Points
0
Hello.
Tapepool does not match offsite after backup.

I ran q occ and it shows the following.

---------- ---- ---------- ---- ---------- ----------- ----------- -----------
OFFSITE 1,456,912 76,526,752. 76,526,696.
00 00
TAPEPOOL 1,457,010 77,483,024. 77,482,976.
00 00

I then ran backup stgpool Tapepool copypool and it resulted in:
NR1214I The backup of the TAPEPOOL primary storage pool
to the OFFSITE copy storage pool is complete. Number of
files backed up: 0. Number of bytes backed up: 0.
Deduplicated bytes backed up: 0. Unreadable files: 0.
Unreadable bytes: 0. (SESSION: 1220)
 
Hi,

From what I can see in your output, is that the offsite pool has less data as the primary pool. There was a problem where the backup storage pool optimization table would get out of sync and not send data to the copy pool when it should be.

The undocumented corrective command is:
RESET BACKUPOPTIMIZATION <volname>

So, if you see that a volume should be sending data to the copy pool you can reset it with the above. Here are the steps if you need to find the problem volumes:

Running the QUERY CONTENT COPIED=NO command on each primary
sequential storage pool volume after the BACKUP STGPOOL command
has been run. If the QUERY CONTENT COPIED=NO command indicates
that there are uncopied files on a volume, run the RESET
BACKUPOPTIMIZATION command on that volume. Once RESET
BACKUPOPTIMIZATION has been run on all affected volumes, run
BACKUP STGPOOL on all affected storage pools to ensure that all
files are properly backed up.
 
Back
Top