cancel
Showing results for 
Search instead for 
Did you mean: 

Backup error on Maxdb 5391 ERR 52012 SAVE error occured, basis_err 3700

Former Member
0 Kudos

Hello gurus

Iam getting the below error when tryind to do complete backup in Maxdb 7.6 running on Linux 10.There were no changes made to the OS as the backups were running fine before:

2010-04-26 14:33:42 5957 ERR 1 Backup + Backupmedium #1 (/dev/st0) Cluster info is lost

2010-04-26 14:42:52 ___ Stopping GMT 2010-04-26 12:42:52 7.6.00 Build 035-123-139-084

2010-04-26 14:46:33 --- Starting GMT 2010-04-26 12:46:33 7.6.00 Build 035-123-139-084

2010-04-26 14:56:22 6290 ERR 11000 d0_aopen Cannot open device, Permission denied

2010-04-26 14:56:22 6290 ERR 11000 d0_aopen Device name '/dev/st0'

2010-04-26 14:56:23 5391 ERR 52012 SAVE error occured, basis_err 3700

2010-04-26 14:56:23 5391 ERR 3 Backup Data backup failed

2010-04-26 14:56:23 5391 ERR 1 Backup + Backupmedium #1 (/dev/st0) Could not open volume

2010-04-26 14:56:23 5391 ERR 6 KernelCo + Backup error occured, Errorcode 3700 "hostfile_error"

2010-04-26 14:56:23 5391 ERR 17 SrvTasks + Servertask Info: because Error in backup task occured

2010-04-26 14:56:23 5391 ERR 10 SrvTasks + Job 1 (Backup / Restore Medium Task) [executing] WaitingT113 Result=3700

2010-04-26 14:56:23 5391 ERR 6 KernelCo + Error in backup task occured, Errorcode 3700 "hostfile_error"

2010-04-26 14:56:23 5391 ERR 1 Backup + Backupmedium #1 (/dev/st0) Cluster info is lost

i have checked the permission on /dev/st0

crw-rw---- 1 root disk 9, 0 Apr 26 14:44 st0

which permission should i look at?

Any ideas are welcome.

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

> 2010-04-26 14:56:22 6290 ERR 11000 d0_aopen Cannot open device, Permission denied

> i have checked the permission on /dev/st0

> crw-rw---- 1 root disk 9, 0 Apr 26 14:44 st0

The MaxDB runs under a special user (sdb), since only the user root and the members of the group disk may write to that device it's clear that this error occurs.

The easiest way to fix this is to put the user sdb (if you use the default user) into the group 'disk'.

Markus