cancel
Showing results for 
Search instead for 
Did you mean: 

SAP ASE Backup issue with NFS mount. write access Error

darshinee
Explorer
0 Kudos
769

Hi , I am taking backup through SAP ASE DB Application using dump command.
I am taking the backup on NFS mount.
But it is giving me below errors. please help in this case. We are qualifying SAP-ASE for our customers
1> dump database test_DB to '/mnt1_nfs/sapase-stu/1.bak'

2> go

Backup Server: 4.172.1.4: The value of 'allocated pages threshold' has been set

to 40%.

Backup Server session id is: 6. Use this value when executing the

'sp_volchanged' system stored procedure after fulfilling any volume change

request from the Backup Server.

Backup Server: 4.41.1.1: Creating new disk file /mnt1_nfs/sapase-stu/1.bak.

Backup Server: 4.141.2.87: [11] The 'lockf' call failed for database/archive

device while working on stripe device '/mnt1_nfs/sapase-stu/1.bak' with error

number 5 (Input/output error). Refer to your operating system documentation for

further details.

Backup Server: 6.53.1.1: OPERATOR: Volume on device '/mnt1_nfs/sapase-stu/1.bak'

cannot be opened for write access. Mount another volume.

View Entire Topic
c_baker
Product and Topic Expert
Product and Topic Expert

Resolution

  1. Determine if the dump is hanging on the file locking by using:

tusc on HP-UX
truss on Solaris
strace on Linux

  1. Start the Backup Server
  2. Run this command: tusc -f -o <output file> -p <pid>
  3. Start dump database.

If the trace output contains a line like shown below then most likely there is an issue with file locking on the NFS server.

lockf(0, 0x2, 0) .........................................
[sleeping]

If dumping to NFS device, file locking must be enabled or it will hang. If file locking is enabled and the hang still occurs then the NFS server may need to be rebooted.

darshinee
Explorer
0 Kudos

Thanks Chris. The locking was not enabled .
when I mounted nfs share , the local_lock=all option was not enabled.
That's why the issue was coming.
When I enabled that option, the Backup worked.

10.198.165.177:/data/col1/sapase-stu on /mnt1_nfs/sapase-stu type nfs (rw,nosuid,nodev,noexec,relatime,sync,vers=3,rsize=1048576,wsize=1048576,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,noac,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.198.165.177,mountvers=3,mountport=2052,mountproto=udp,local_lock=all,addr=10.198.165.177,user)
Thanks a lot everyone for timely replies.
Regards,
Punya