path /backup/DB_BACK already in use by backup medium 27

[Former Member]

Hi all,

after a

-

---

RTEWrapper_VolumeIO+noPIC.cpp:694
detach of volume 27 failed
RTEIO_StreamMedium+noPIC.cpp:1332
"medium /backup/DB_BACK with number 27 cannot be closed"
close error 1
error occured, basis_err 3700
Kernel_Administration+noPIC.cpp:1468
Data backup failed
Backupmedium #1 (/backup/DB_BACK) close failed
Backup error occured, Error code 3700 hostfile_error
Kernel_Administration+noPIC.cpp:1468
Data backup failed

-

---

I get a:

-

---

RTEIO_StreamMedium+noPIC.cpp:720
create of medium /backup/DB_BACK of type 1 impossible
RTEIO_StreamMedium+noPIC.cpp:954
"path /backup/DB_BACK already in use by backup medium 27"
error occured, basis_err 3700
Kernel_Administration+noPIC.cpp:1468
Data backup failed
Servertask Info: because Error in backup task occured
Job 1 (Backup / Restore Medium Task) [executing] WaitingT219 Result=3700
Error in backup task occured, Error code 3700 hostfile_error
Backupmedium #1 (/backup/DB_BACK) Cannot create backup medium
Backup error occured, Error code 3700 hostfile_error
Kernel_Administration+noPIC.cpp:1468
Data backup failed

-

---

Is there an other possibility to get the backup medium working again then restarting the database?

How do I close backup medium 27?

Thanks a lot

Christian

[Former Member]

A bit more information perhaps?

Which operating system?

Which backup tool?

As a first guess:

Is backup file system /backup/DB_BACK full perhaps?

Any other problem with it?

Is /backup/DB_BACK a filesystem at all, or what else?

(Sorry, my crystal ball is a bit dim this morning.)

[Former Member]

Hi Joe,

I am sorry, but backuptool and operating system are irrelevant for this problem. (By the way I am using SLES11 and MAXDB internal backup template to file.)

The backup template backs up via network to file where is enough space.

Other backup templates are working to the same lokation (other file).

The backup template is configured to use overwriting!

I just had this error once ago, the database believes that the backup is still in use (so there must be a socket, semaphore, somewhat) to be deleted to get the media working again (which a db restart would do).

Removing the old backup file would not help.

Removing and rereating the backup template would not work. (already tested)

But is there a "dbmcli release_backup_media <nr>" or something like command to reset an open backup media?

Best regards

Christian

[Former Member]

Hello Christian,

thanks for explaining.

Now it looks like some network problem, and I'm afraid I can't help here.

Is /backup/DB_BACK an NFS mount btw?

We too are struggling with NFS mounts in SuSE Linux sometimes, and there are (luckily rare) cases were we haven't found any other solution than waiting for hours, or restarting the server....

regards

[Former Member]

Hi Joe,

I got a timeframe for restarting the database...

As I said, this worked...

Best regards

Christian