cancel
Showing results for 
Search instead for 
Did you mean: 

MaxDB tape backup permissions problem.

Former Member
0 Kudos

I am trying to do a MaxDB (7.6) backup to tape.

I've set up a backup medium for full data backup to tape.

The tape device is:

crw-rw---- 1 root disk 9, 1 Mar 26 11:48 /dev/st1

Whatever I try to do, I get this error in knldiag:

2007-06-19 13:14:18 17200 ERR 11000 d0_aopen Cannot open device, Permission denied

2007-06-19 13:14:18 17200 ERR 11000 d0_aopen Device name '/dev/st1'

2007-06-19 13:14:18 4450 ERR 52012 SAVE error occured, basis_err 3700

2007-06-19 13:14:18 4450 ERR 3 Backup Data backup failed

2007-06-19 13:14:18 4450 ERR 1 Backup + Backupmedium #1 (/dev/st1) Could not open volume

2007-06-19 13:14:18 4450 ERR 6 KernelCo + Backup error occured, Errorcode 3700 "hostfile_error"

2007-06-19 13:14:18 4450 ERR 17 SrvTasks + Servertask Info: because Error in backup task occured

2007-06-19 13:14:18 4450 ERR 10 SrvTasks + Job 1 (Backup / Restore Medium Task) [executing] WaitingT136 Result=3700

2007-06-19 13:14:18 4450 ERR 6 KernelCo + Error in backup task occured, Errorcode 3700 "hostfile_error"

I know this is a simple Linux permissions issue, because if I do:

chmod o+rw /dev/st1

the backup works fine.

I'm not happy with this as a solution because

a) I don't want to mess with the device file configuration

b) I'm not confident it would survive a reboot.

The backup process runs as user sdb, and I have added sdb to group disk.

It seems to me this should solve the problem, but it doesn't.

Can anyone tell me why, or what I should do to resolve it?

I'm running on Linux, and uname -or gives:

2.6.9-42.0.3.ELsmp GNU/Linux

TIA

Chris Harris

I'm running on Linux, and uname -a gives:

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Chris,

just a 'dumb' question:

Did you restart the database after adding sdb in /etc/groups to the the group 'disk'?

Henrik

Former Member
0 Kudos

Henrik,

Not a dumb question - no I hadn't - it didn't occur to me that I needed to. I would have expected the os to check the permissions for the process user at the point when it tried to service the request to open the device.

I guess I was wrong - restarting the db solved the problem.

Thanks!

Chris

Answers (0)