Forum Discussion

Farooq's avatar
Farooq
Level 2
2 months ago

SAP Oracle backup is taking longer than usual

Hello Team,

We have a SAP oracle server which is taking more than 9 hours, previously it was taking 4 hours to complete, currently we are using 8.3.0.1 version for client, master and media, The memory is also available. We changed storage unit as well but no luck.

  • Hi Farooq 

    Hard to be specific as there are too many variables.

    You will need to determine what has changed (something must have). It could be a slow process. As as suggestion start looking at these:

    • The entire network path (has a bonded link partially failed for instance?)
    • DB size (has this suddenly grown substantially - although a 2 fold increase seems unlikely)
    • Any OS or DB patching on the DB server,  or OS patching on the media server.
    • Any recent introduction of any packet inspection in the path (firewall/IDS/IPS systems)
    • Degraded disk arrays (either media server or DB server)

    Good luck.

     

  • Hello David, 

    Thanks for your reply, As per the BASIS team recently OS patching has been done on the server and also previously it was 18TB and then SAP team resized it to 16TB. Post this we are facing this backup slowness issue. what are the possible resolutions ?

    • Hamza_H's avatar
      Hamza_H
      Moderator

      You may also want to check name resolution if there were any changes and check TN’s regarding slow oracle backups

      These logs may help
      Dbclient and bphdb logs on the client

      bpbrm and bptm logs
      PS; , the netbackup version is no longer supported 

       

    • davidmoline's avatar
      davidmoline
      Level 6

      Hi Farooq 

      I'd be investigating what patches were installed and what affect these could have on access speed (probably nothing, but should be looked at). Secondly, when the SAP team did the resize, how was this done? Have they compressed the database to achieve the space saving? If the target for the backup is a deduplicating device (MSDP, DataDomain etc.) then writing compressed data to it will require more time as the data will not dedupe well, so more data will need to be sent over the wire.

      Looking at your original post, you were able to backup 18TB in 4 hours - this translates to an effective transfer rate of approx 1.3GB/s (now if a dedupe target is used, this is not necessarily the real transfer rate, which depends on the dedup ratio achieved). Now the DB has been changed - the effective transfer rate has dropped to about 530MB/s. 
      What is the network speed of the interface(s) used for backup - a 10GBE interface would most likely max out at 800MB/s (~9Gbps). 

      Cheers

    • davidmoline's avatar
      davidmoline
      Level 6

      Hi Farooq 

      How was the DB size reduced to 16TB? Was it compressed? What is the target device for your backups? If a dedupe device (e.g. MSDP/Data Domain), then compressed data won't dedupe well, and so more data will need to be sent from the client - this could explain the slowdown. 

      Cheers

  • I would say Involve your oracle team and create a case with veritas to investigate it further.