Hi Folks 

I have 11 Protection groups configured to 30 days disk backups and then on 1st of every month that data to be written to tape. 

Means 

Short Term retention (Disk) : 30 Days

Long Term retention (Tape) : 5 Years (To be written on 1st of every month) 

Now I have 3 TB each tape in tape library, on tape job time - express full backups size is varying between 2.5 TB to 3.5 TB.

Through tape optimization I have configured all tape backups to single tape, so when data size is 2.5 TB that is writing properly.

But when data size is more than 3 TB on tape job time, it make tape offsite ready after filling it and the jobs having restof 500 Gigs data are failing. Is there any way so I can calculate data size before 1st of month so I can decide either to send it to single tape or two !

• Moved by Mike JacquetMicrosoft employee, Moderator 13 hours 56 minutes ago

Anyone can help this out !

HI,

<snip>
But when data size is more than 3 TB on tape job time, it make tape offsite ready after filling it and the jobs having restof 500 Gigs data are failing. Is there any way so I can calculate data size before 1st of month so I can decide either to send it to single tape or two !
>snip<

I think you should tackle why the tape backup job is failing rather than focusing on how much data needs backed up.   What are the details of the failed tape backup job after the first tape if filled ?

Sorry for confusion Mike. 

From your point now I sumarize that if tape filled up then pending job should had to written on new tape ! (correct me if I am wrong)

I checked logs now, these jobs failed due to modifying protection groups. I understand now thats why these job failed and If someone didn't do this then that pending data was supposed to written new tape. 

But, still is there any way to guess data size? I dont want to fill one tape with 3TB and use 2nd tape for another 200 Gigs. 

• Edited by Vijay MC 13 hours 6 minutes ago

Hi,

You can run this SQL script to show used replica size in GB which is what should be written to tape during a backup.  Of course, this will not take into account compression, and the size may differ since we always backup from shadowcopy which may be more or less data than current replica used space.

select distinct Volume.GuidName as Replica_Guid,Replica.Validity,Volume.MountPointPath,round (replicavol.ReplicaUsedSize/1024.0/1024.0/1024.0,2) as UsedReplicaGB,server.servername--,(cast(datasource.datasourcename as nvarchar(max)))
from tbl_SPM_Volume Volume 
join tbl_SPM_VolumeSet VolumeSet on VolumeSet.VolumeSetId=Volume.VolumeSetId 
join tbl_PRM_LogicalReplica Replica on Replica.PhysicalReplicaId=VolumeSet.VolumeSetId 
join dbo.tbl_PRM_ReplicaVolume ReplicaVol on VolumeSet.VolumeSetId=replicavol.ReplicaId 
join tbl_IM_Datasource Datasource on Datasource.DatasourceId=Replica.DatasourceId 
join tbl_AM_Server Server on Server.ServerId=Datasource.serverid 
join tbl_SPM_Extent Extent on Extent.GuidName=Volume.GuidName 
join tbl_SPM_Disk disk on disk.DiskID=Extent.DiskID 
and Replica.Validity in (1,2) 
and volume.usage in (1)

Thanks for script. 

This showing sum of all replicas = 3352.6 GB. I think I will have to optimize tapes into 2 or will have to de-select unwanted backups to tape. 

Thanks a lot for this script.

• Edited by Vijay MC 11 hours 3 minutes ago