This issue has been solved.

Warning bpbrm (pid=16851) from client xxxxxxx: WRN - Could not reset access time of /rman/one. Errno = 1: Operation not permitted

Created: 16 Jan 2013 • Updated: 08 Mar 2013
Vivek Sahu's picture
Login to vote
0 0 Votes

I am trying to configure backup for /ram (NFS Mount point), Backup job is completing successfully with below error. Please advice.

Netbackup Master server version : 7.1

Client OS : Linux

 

01/16/2013 04:56:49 - Warning bpbrm (pid=16851) from client xxxxxxx: WRN - Could not reset access time of /rman/one. Errno = 1: Operation not permitted
01/16/2013 04:56:49 - Warning bpbrm (pid=16851) from client xxxxxxx: WRN - Could not reset access time of /rman/two. Errno = 1: Operation not permitted
01/16/2013 04:56:49 - Warning bpbrm (pid=16851) from client xxxxxxx: WRN - Could not reset access time of /rman/three. Errno = 1: Operation not permitted
01/16/2013 04:56:49 - Info bptm (pid=16853) backup child process is pid 16862
01/16/2013 04:56:50 - Warning bpbrm (pid=16851) from client xxxxxxx: WRN - Could not reset access time of /rman/four. Errno = 1: Operation not permitted
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_1_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_2_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_3_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_4_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_5_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_6_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_7_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_8_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_df_20130113_9_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file /rman/backup/cshrddb/cshrddb_al_20130113_10_1. Errno = 13: Permission denied
01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file/rman/backup/cfmemdb/cfmemdb_df_20130113_1_1. Errno = 13: Permission denied

Quick Look Solution

Check share permissions on

Check share permissions on source server as well as mount options on NBU client. 

Backup is running as root and will need sufficient permissions to read data.

Please do the following while logged in as root on the client:

ls -l /rman/backup/cshrddb/

Any reason why this filesystem cannot be backed up from source server?

Filed Under

Comments

Nagalla's picture
Nagalla
Certified
Certified
16
Jan
2013

01/16/2013 04:56:51 - Error

01/16/2013 04:56:51 - Error bpbrm (pid=16851) from client xxxxxxx: ERR - Cannot open file/rman/backup/cfmemdb/cfmemdb_df_20130113_1_1. Errno = 13: Permission denied

Check netbackup client where the NFS fs is mounted, does have the Premission to the path /rman/backup/cfmemdb/

 

PS:- better option is to take the backup from the NFS server as a local file system, it avoids lot of issue, even data travel in the Network.

Marianne's picture
Marianne
Trusted Advisor
Accredited
Certified
16
Jan
2013
SOLUTION

Check share permissions on

Check share permissions on source server as well as mount options on NBU client. 

Backup is running as root and will need sufficient permissions to read data.

Please do the following while logged in as root on the client:

ls -l /rman/backup/cshrddb/

Any reason why this filesystem cannot be backed up from source server?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Vivek Sahu's picture
Vivek Sahu
Certified
Certified
17
Jan
2013

Many thanks for your reply

Many thanks for your reply Marianne & Nagalla.

We didn't have all access to customer's client server, I had a discusstion with them and found out that it had to do with the permissions on the datafiles, They are owned by user oracle & they were on Mode 640 (USER-read/write, GROUP-readable, but not WORLD-readable)

The NetBackup client runs as root, but it is unable to read the files because, by default, root has no special permissions on this NFS mount.

Customer has change the way the /rman mount is exported, so that is has root permissions. Now I have kicked off the backup job which is picking up data :)

Now only below error is coming : 
 

 

01/16/2013 04:56:49 - Warning bpbrm (pid=16851) from client xxxxxxx: WRN - Could not reset access time of /rman/one. Errno = 1: Operation not permitted.

I believe for this we may want to add DO_NOT_RESET_FILE_ACCESS_TIME to client server's bp.conf file??

Marianne's picture
Marianne
Trusted Advisor
Accredited
Certified
17
Jan
2013

Correct. See http://www.syman

Correct.

See http://www.symantec.com/docs/TECH163159

 

Cause

NetBackup cannot reset the File Access time back to the original setting

Solution

1- By Default NetBackup reset the access time of the file after reading/backing up the data BACKUPS.

   The default behavior is to reset access time of backups. (NetBackup stores access time prior to backup, then after backuping up the file , it resets the access to the original setting).

   Resetting access time is only valid if the following condition is set;

     - The NFS filesystem is not mounted with 'noatime' flag. This flags disable access time tracking for the filesystem.

       - The file System access permission is set for "root" user to read & write

2- The main reason for this message that NetBackup cannot reset the File Access time back to the original setting

      NetBackup does not have Write permission or the file system is mounted with 'noatime' flag.

3- The Best Solution is to allow NetBackup to reset access time i.e. modify the NFS File System setting to allow write access for root and disable 'noatime' flag.

4- If the Customer require to disable NetBackup from resetting the Access Time

      then there is an option which disable NetBackup Default setting by adding 'DO_NOT_RESET_FILE_ACCESS_TIME ' to the client's /usr/openv/netbackup/bp.conf file.

     REFERENCE: VERITAS NetBackup Administrator Guide, Volume I

 

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links