Hi Steve, Sorry for a late answer to your question. Here is your answer to your question.
bcfiler1a> df -S vol_xenbackup1 Filesystem used total-saved %total-saved deduplicated %deduplicated compressed %compressed /vol/vol_xenbackup1/ 162628316 188334552 54% 188334552 54% 0 0% If you take Total-Save + Deduplicated value then do you got the amount of data that NetApp SnapMirror and TSM should backup. And when I count does number together do I get a total backup amount of approx. 350GB. PS: Sorry to tell you, NetApp is not a good investment if you want to be able to restore the data. Thanks Christian -----Ursprungligt meddelande----- Från: Schaub, Steve [mailto:[email protected]] Skickat: den 31 januari 2013 19:30 Till: [email protected] Ämne: Re: Vol size discrepency for SnapMirror2Tape of NetApp Here is what the filer admin sent me about the volume in question: Here are the volume options: bcfiler1a> vol options vol_xenbackup1 nosnap=off, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off, ignore_inconsistent=off, snapmirrored=off, create_ucode=on, convert_ucode=on, maxdirsize=190054, schedsnapname=ordinal, fs_size_fixed=off, guarantee=volume, svo_enable=off, svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off, no_i2p=off, fractional_reserve=0, extent=off, try_first=volume_grow, read_realloc=off, snapshot_clone_dependency=off, dlog_hole_reserve=off, nbu_archival_snap=off bcfiler1a> vol status vol_xenbackup1 Volume State Status Options vol_xenbackup1 online raid0, flex create_ucode=on, convert_ucode=on, sis fractional_reserve=0 64-bit Volume UUID: dcfc597e-84cd-11e1-a591-00a09818fdb8 Containing aggregate: 'bcfiler1a_aggr2' bcfiler1a> aggr status aggr2 aggr status: No aggregate named 'aggr2' exists bcfiler1a> aggr status bcfiler1a_aggr2 Aggr State Status Options bcfiler1a_aggr2 online raid0, aggr 64-bit Volumes: vol_xenbackup1, vol_marketing5 Plex /bcfiler1a_aggr2/plex0: online, normal, active RAID group /bcfiler1a_aggr2/plex0/rg0: normal, block checksums bcfiler1a> df -S vol_xenbackup1 Filesystem used total-saved %total-saved deduplicated %deduplicated compressed %compressed /vol/vol_xenbackup1/ 162628316 188334552 54% 188334552 54% 0 0% bcfiler1a> sis status Path State Status Progress /vol/vol_xenbackup1 Enabled Idle Idle for 88:11:00 bcfiler1a> snap sched Volume vol0: 0 2 6@8,12,16,20 Volume vol_xenbackup1: 2 2 0 bcfiler1a> snap reserve Volume vol0: current snapshot reserve is 20% or 62914560 k-bytes. Volume vol_xenbackup1: current snapshot reserve is 35% or 146800640 k-bytes. Thanks, -steve ***public*** -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Christian Svensson Sent: Thursday, January 31, 2013 3:35 AM To: [email protected] Subject: [ADSM-L] SV: Vol size discrepency for SnapMirror2Tape of NetApp Hi Steve, Have you check the dedup level? And have you also verify that no data are encrypted? Because our NetApp we had before allocated extremely amount of data in our TSM server. And what volume are you backing up? The Snapshot volume or the true volume? Thanks Christian ________________________________________ Från: Schaub, Steve [[email protected]] Skickat: den 30 januari 2013 19:34 Till: [email protected] Ämne: Vol size discrepency for SnapMirror2Tape of NetApp TSM Client Version 6, Release 2, Level 4.0 TSM Server Version 6, Release 2, Level 4.0 IBM rebranded NetApp filer Data ONTAP Release 8.1.1 7-Mode Running full volume SnapMirror2Tape backups on our filers, and 1 out of the dozen or so volumes is reporting very different sizes. When I run the Powershell command "Get-NaVol", this volume show these sizes: Name Size Used vol_xenbackup1 279172874240 166531391488 but the TSM log after running the SM gives vastly different sizes (again, just for this volume, the other volumes are at least reasonably close): xenbackup1 backup: ANR0986I Process 2001 for NAS SNAPMIRROR BACKUP running in the FOREGROUND processed 1 items for a total of 334,846,476,288 bytes with a completion state of SUCCESS at 00:10:46. Executing a "Q nasbackup" for this vol shows this: Node Name Filespace Object Type Object Creation Mgmt Class Image Name Size (MB) Date Name Storage Pool Name ------------ ----------- ----------- --------- ---------- ---------- ---------- BCFILER1A /vol/vol_x- SnapMirror 319,373.5 01/27/2013 NAS ST06_TAPE- enbackup1 22:00:52 _P01 Our filer admin has checked everything on all the volumes and doesn't see anything different in the config of this vol. All of our vols have compression and dedupe turned on, but this vol is the only one that TSM is not reporting the size correctly. The SM backup is going over 10GBe to a diskpool, not tape. Anyone seen anything like this, or have an idea what else to check? Thanks, Steve Schaub Systems Engineer II, Windows Backup/Recovery BlueCross BlueShield of Tennessee ----------------------------------------------------- Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm ----------------------------------------------------- Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
