NetBackup 7.0.1 SAP backups slowness running two differente jobs
thanks in advance for any help you give me.
I'm running a NetBackup 7.0.1 solution based on a master/media server (with 10T) on RHEL 5.4 and two other media with same storage again on RHEL.
Clients are all windows (2k8,2k8R2 and 2k3).
Policies i've set are for OS (inc/full) and SAP (full/arch logs).
Target MEDIA are configured as load balance for specific policies, but this is not the major issue.
Well, for all the SAP policies, that use brbackup (started by a script .bat on the client) i found something strange.
The case is for two different servers , called SVR1 and SVR2.
SVR1 into the same network of the media, SVR2 into another network, always reachable, but with low bandwidth (trough FW to be precise).
The strangeness is regarding the throughput when the backup starts, because even if the speed of SVR2 is clear to be not so high due the FW in the middle, also the SVR1 lowered the speed for the time they are running in parallel !
Then, after SVR2 finish the backup, because it is not so big, the SVR1 start to raise speed until the up limit of the network.
I've tested it several times, with several servers, SAP backups are always so, it seems to be a real "behaviour", but not clear for me.
The only workaround i found it is to run SVR2 before and let finish it alone, then start SVR1 alone again after any other.
That is the strategy i've adopted also for other backup for SAP where same server are on different network, or for any other reasons different bandwidth exists.
In other words, SAP backups need to be runned alone, one server by one, first start, then finish, second start, then finish, third...and so on.
Of course this create a lot policies and overlap of BU window is easy to hit, definitively more complexity to manage.
Does anyone know if it is a real issues that can be solved or addressed differently?
Is it possible within a policy to start a server before another and not overlap them?
"Limit job per policy rule" is not what i'm asking for, because since there 4 streams for single server, it appears that sometime , randomly, one server start 2 streams, the other too,and the remaining streams are into the queue.
Not a real solution.