Our Exchange Backup running very slow since 99hrs but it will finished successfully with our any error, but question is why it's taking to much time finished.
Backup Environment Details.
Master Server Name:netbackup.domainname.com
OS:- Windows 2008 R2 64 Bit Enterprise
NBU Version:- 220.127.116.11
Cleint Name:- Dag1.domainname.com
OS: Windows 2008 R2 64 Bit Enterprise
Excahnge Version:- 2010
NBU Version:- 18.104.22.168
Note:- Netbackup Application License got Expired on 2015 afer that my all backup running very slow.
please find the below job Details
3/5/2020 10:49:00 AM - Info nbjm(pid=7504) starting backup job (jobid=1908416) for client DAG1, policy MB07_EX_Backup, schedule Daily
3/5/2020 10:49:01 AM - estimated 0 Kbytes needed
3/5/2020 10:49:01 AM - Info nbjm(pid=7504) started backup (backupid=DAG01_1583394540) job for client DAG1, policy MB07_EX_Backup, schedule Daily on storage unit Netbackup_MSDP_DiskPool_STU
3/5/2020 10:49:02 AM - started process bpbrm (10752)
3/5/2020 10:49:18 AM - Info bpbrm(pid=10752) DAG1 is the host to backup data from
3/5/2020 10:49:18 AM - Info bpbrm(pid=10752) reading file list for client
3/5/2020 10:49:18 AM - connecting
3/5/2020 10:49:24 AM - Info bpbrm(pid=10752) starting bpbkar32 on client
3/5/2020 10:49:24 AM - connected; connect time: 0:00:06
3/5/2020 10:49:41 AM - Info bpbkar32(pid=3068) Backup started
3/5/2020 10:49:41 AM - Info bptm(pid=3724) start
3/5/2020 10:49:43 AM - Info bptm(pid=3724) using 262144 data buffer size
3/5/2020 10:49:43 AM - Info bptm(pid=3724) setting receive network buffer to 1049600 bytes
3/5/2020 10:49:43 AM - Info bptm(pid=3724) using 30 data buffers
3/5/2020 10:49:44 AM - Info bpbkar32(pid=3068) change time comparison:<disabled>
3/5/2020 10:49:44 AM - Info bpbkar32(pid=3068) archive bit processing:<enabled>
3/5/2020 10:49:46 AM - Info bpbkar32(pid=3068) INF - waiting for mount mutex...
3/5/2020 10:49:47 AM - Info bptm(pid=3724) start backup
3/5/2020 10:50:19 AM - Info bptm(pid=3724) backup child process is pid 8528.11424
3/5/2020 10:50:19 AM - Info bptm(pid=8528) start
3/5/2020 10:50:19 AM - begin writing.
Please help on the above issue.
Can't see any problems with what you have posted.
Try here first and see what you can find, and pick out the bits that look interesting to you from your logs:
Once you've had a good rummage through the logs, then post back here with the parts that might reveal any underlying issues.
Any evidence of previously much faster throughput in KB/s?
You do mean slower KB/s, and not just simply longer elapsed active duration, right?
Define slow? Define acceptable speed? Define fast?
Are all Exchange backups slow KB/s? Are any acceptable KB/s?
This doesn't look like an Exchange question to me, as it took only 1 minute to get to "begin writing." If it then takes an excessively long time to transfer the data, then that's what you need to solve.
If you take a verbose bpbkar log on the Exchange server, you can see how big each data file is, and how long it takes to read it and send the data to bptm. Look for "STAN". The next line says, for example, that bpbkar32 has finished reading X bytes of AAA.edb. The time between the two lines is how long it took to send the data to bptm.
Actually almost all fileserver,Application,Exchage,vm and rman backups are running very slow. may i know that if NBU License got expired is effect to our backup environment?
If you bought Perpetual licenses, then it is impossible for licenses to expire.
If you run license report on your master, you will see that expiration date is NEVER.
Your Maintenance may have expired, which means that you cannot log support calls and that you are not entitled to free upgrades or patches.
About slow backups - you need to troubleshoot one system at a time - look at capabilities of each component in the chain.
Media server - sufficient resources to ensure max possible throughput? (memory, cpu, NIC, backup storage and connection to media server)
Network between client and media server
Client capabilities to read, generate and send data stream
Fragmentation on client disks
There is an old NetBackup Performance Tuning Guide that should be still valid for your environment.
AFAIK all normal (traditional license AND capacity license) NetBackup base licences are "perpetual use", i.e. you own the right to continue using those versions forever.
What you pay for annually is "support renewal", i.e. a combination of "support" plus the option for "renewal" of versions (i.e. license key version upgrades).
So, AFAIK, you are free to keep running your versions for as long as you like.
I've worked with NetBackup for quite some time now, and been involved in many licence reviews and renewals, and I've never heard of the software going slow simply because the support element has lapsed - I've never seen that for myself, and never heard anyone else say that, before today.