SQL Backup

[H_Sharma]

Hello Experts,

We have a sql policy that is getting failed with 48 error code. However, its flat file backup is successfull with other policy.

I checked both the clients name in both the policies are mentioned correctly same. Storage units are same.

There was one below eror in SQL backup and its also ruuning a job with None schedule in console.

Pls help.

Unable to write progress log </C/ProgramÀ Files/Veritas/NetBackup/Logs/user_ops/dbext/logs/26152> on client Policy=MS_SQL_Server-DB_Hot- Sched=NONE

[RamNagalla · Accepted solution]

Does the Master server able to resolve the IP address of the SQL host? you need to make sure that netbackup master server is able to resolve the IP address of the SQL server.. (FS backups still work even it is not reslovig it)

does this backup is scheudled to run from Netbackup or from SQL host using Scheduler?

[watsons]

Please check this old thread out for a similar error: 

https://www.veritas.com/community/forums/sql-2008-failed-unable-write-progress-log-cprograma-filesveritasnetbackuplogsuseropsdbextlogs?page=0

Error 48 is a network-related error, database backups generally use more network ports than filesystem backup, so ensure you have allocated more ports for it. 

[Marianne]

As per Ram's post above, Db backups work different from flat file backup. Flat file backup only needs comms between media server and client. Db backups need comms between master and client. Use bpclntcmd on master and client to test forward and reverse name lookup.

[Pangal]

Kindly confirm whether the hostname in client configuration and sql script and policy name is same (Same case)

[winter_prince]

Can you execute the following commands from master and media server and post the output...

/usr/openv/netbackup/bin/admincmd/bptestbpcd -client <your failing SQL client> -verbose -debug

Also, confirm the following:

• Network Communications between Client, Media Server and Master (All of them should be able to communicate with each other - ping tests and traceroute tests)
• Media Server Access Entry: Master and Media Server should be present in the client's Media server or server list.

This is most likely a basic issue.. Please revert.