Client - Media - PureDisk Linux network traffic
Hello everyone. We have a backup solution and I am trying to find a bottleneck. Configuration is as follows: Veritas SFHA clustered Master server running NBU 7.5.0.6 on RHEL6.1. Number of Media servers. And 3 pairs of PureDisk 6.5.5 pools as a storage servers. My concern is: How does network traffic flow during backup assuming clientside deduplication is enabled? I tried tcpdump and appears that it is client - media - puredisk and vica-versa. But there are nbstproxy processes. Appreciate on any assistance. Thank you.Solved4.1KViews0likes2Comments
About Pure Disk
Hi All, Kindly let me know the following few questions about pure disk. 1)what is pure disk? 2)About pure disk architecture? 3)About pure disk deduplication? 4)About pure disk web user interface? 5)Can i know the role of vssadminlist writers related to system state backup failures in pure disk.Solved3.8KViews3likes2Comments
SLP Duplication Behaviour
Master Server ( nbu01 ) Windows 2008 NetBackup Master 7.5.0.7 Media Server ( nbu02 ) Window 2008 NetBackup Media 7.5.0.7 MSDP with puredisk Setup storage server load balancing for dedupe pool nbu01 and nbu02 setup SLP backup to disk then duplicate to tape both nbu01 and nbu02 connected to the same tape library ofcourse with SSO enable All backup and duplication went well but found out that during duplication to tape, always server nbu01 trigger to job even the tape storage unit is connected to nbu02. I want to know if duplication job trigger from nbu01, let say backup image is 100GB, from the dedupe guide, it say that it will always rehydrate the data where the dedupe pool server is, so means nbu02, so do this means that it will send 100GB data to nbu01, then nbu01 will send back 100GB of data back to nbu02, because i select tape storage unit that connected to the nbu02, and write to tape. If above is true, means my bottleneck will be at the LAN, and how do i force only use nbu02 during duplication job. I also planning to remove the load balancing, since i dont see much help on the backup and duplication, but i still have job queuing for duplication. If i inactive those job, remove the nbu01 from the load balancing, and activate backup duplication, will the duplication job still look for nbu01 ? or i need to cancel all job, and do manual duplication ? anyone please help.1.3KViews0likes2Comments
Netbackup Appliances 5230 with PureDisk: How many streams?
Hi all, We recently migrated to Netbackup Appliances running Netbackup 7.6.0.1 (Appliance version 2.6.0.1 ) We are running 2 appliances per site, each site is its own NBU domain (We use AIR to replicate). Each appliance is configured with a 70TB PureDisk volume. We are quite new to PureDisk that is running on these systems, but at this moment they are limited to 80 streams maximum in the diskpool object (Which seems pretty low to me) At the moment we are running out of resources due to this maximum that has been set. What is the maximum streamcount a 5230 Appliance PureDisk can safely handle? Note that we are using AIR to replicate all our images, but replication is being done during the day, not during backup times... Any advice is greatly appreciated! Thanks!1KViews1like2Comments
NBU-Duplication issue
hi guys, i'm facing a strange issue when duplication images from my AdvDisk... if i run backup with my Netbackup 7.5.0.5 to Advdisk its successful and duplicating simultaniously to puredisk the performance is OK up to (87000KB/SEC) if i run backup with my Netbackup 7.5.0.5 to Advdisk its successful and duplicating simultaniously to tape LTO4 the performance is ok OK up to 70000KB/SEC) BUT if duplication to both PDDO and LTO4 in the same time the performance is 43 000 KB/SEC i spent many days reading the logs ( nbsl, nbpem, nbjm nbrb , nbstserv ,vxlogcfg etc ) i couldnt find any errors or a source limiting the performance all what seems to me strange is when writing to tape the bptm reporting in more than 300 lines : write_data: writing block shorter than BUFF_SIZE, 65536 bytes write_data: writing short block, 65536 bytes, remainder 0 seems it's related to what previously found : DUP_BLKSIZE ( in bptm) are by default set to 65536 (64K) so when we duplicate to tape the read requests pass the data in 64 , and the backups written to Advanced disk normally on the disk array the data is being written in 512K if it’s not more, if we will duplicate by passing data in 64K which is insufficient because it will require more (Input/Output Per Second) = the performance decreasing ….. IS it related ???? the Master is an AIX, Appliances 5220 any help sugesstion ? thank you in advance780Views0likes0Comments
How to determine if CR rebasing completed
Hi, I am trying to find a way to find out if the post 6.6.3a PureDisk upgrade Content Router rebasing has completed. It is quite easy to check with the crcontrol if the rebasing option is enabled or disabled at all but I would like to know if the rebasing is still "in progress" or is this "completed". I am aware that this rebasing runs in backgroud and not 24/7 but how to check if all CR entries have been rebased?? Thanks!1.8KViews1like4CommentsCLI Command For Dedup Rates
NBU Experts, Do any of you know if there is a CLI command that can tell the dedup rate for all the images created, and stored in a PureDisk pool? For examaple, if I run bpimagelist on the master server I get some good info, but not the dedup rate for each image. Thanks, AVazquez2.6KViews0likes7CommentsMSDP question re full at 96% vs. high water mark at 98%
When does full disk processing take place? At 96% or 98% ? And doesn't this all imply that a high water mark is probably best set to something like 90% (max)or probably (85%) so that clenup can occur before it gets full. If so, then why is teh default 98% Page 68 of the NetBackup v7.5 Deduplication Guide: http://www.symantec.com/business/support/index?page=content&id=DOC5187 ...says this: About deduplication storage capacity The maximum deduplication storage capacity is 64 TBs. NetBackup reserves 4 percent of the storage space for the deduplication database and transaction logs. Therefore, a storage full condition is triggered at a 96 percent threshold. For performance optimization, Symantec recommends that you use a separate disk, volume, partition, or spindle for the deduplication database. If you use separate storage for the deduplication database, NetBackup still uses the 96 percent threshold to protect the data storage from any possible overload. If your storage requirements exceed the capacity of a media server deduplication node, do one of the following: - Use more than one media server deduplication node. - Use a PureDisk storage pool as the storage destination. A PureDisk storage pool provides larger storage capacity; PureDisk also provides global deduplication. See “About the deduplication storage destination” on page 22. Only one deduplication storage path can exist on a media server. You cannot add another storage path to increase capacity beyond 64 TBs. ...but says this on page 82: High water mark The High water mark setting is a threshold that invokes the following actions: - The High water mark indicates that the PureDiskVolume is full. When the PureDiskVolume reaches the High water mark, NetBackup fails any backup jobs that are assigned to the storage unit. NetBackup also does not assign new jobs to a storage unit in which the disk pool is full. NetBackup also fails backup jobs if the PureDiskVolume does not contain enough storage for its estimated space requirement. - NetBackup begins image cleanup when the PureDiskVolume reaches the High water mark; image cleanup expires the images that are no longer valid. NetBackup again assigns jobs to the storage unit when image cleanup reduces the PureDiskVolume capacity to less than the High water mark. The default is 98%.2.1KViews0likes1Comment
