Highlighted
Absent Member.. Absent Member..
Absent Member..
299 views

Mount request blocks jobs

Jump to solution
i,
i have the following problem:
15 backup tasks, that are starting and queing in the night.
If one of them has no medium and starts a mount request, all other won't start until mount request is confirmed. If it is not confirmed, after a couple of hours, all jobs will abort.
How can i change this, let me say, that after one hour the mount request is aborted and the other jobs can be done?
Regards
rainer
0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.
Absent Member.
Hi,

When the system detects the requirement for the mount it waits for the time specified in Delay. It then runs the script specified.

What you need to do is to change the Delay time to be 60 and change the script to one that will abort the backup instead.

I suggest that you make a copy of mount.bat and call it abort.bat and replace the last line with:

omniabort -session %SESSIONKEY%

Purists will say that you should put in the full path to omniabort but that should work.

Once this is in place you can change the script specified for the device(s) from mount.bat to abort.bat

Jeremy

View solution in original post

7 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..
Sorry,
Accidental double post

0 Likes
Highlighted
Absent Member.
Absent Member.
Hi,

Change the default mount request script for the logical device to something like:

(the example is from a Unix Cell Manager).

#!/sbin/sh

THIS=${0}
USER=${1} # unix login of user who started the backup
GROUP=${2} # unix group of user who started the backup
HOSTNAME=${3} # host where the backup was started
STARTPID=${4} # pid of the backup process
DEVNAME=${5} # logical device that generated mount request
DEVHOST=${6} # host to which the device is attached
DEVFILE=${7} # pathname of the physical device
DEVCLASS=${8} # device type number
DEVCLASSNAME=${9} # device type name
shift 9;
MEDID=${1} # medium id of the reqested medium
MEDLABEL=${2} # label of the requested medium
MEDLOC=${3} # location of the requested medium
POOLNAME=${4} # pool name to which requested medium belongs
POLICY=${5} # media allocation policy
MEDCLASS=${6} # media type number
MEDCLASSNAME=${7} # media type name
SESSIONKEY=${8} # sessionkey of the running session

/opt/omni/bin/omniabort -session $SESSIONKEY

Highlighted
Absent Member.. Absent Member..
Absent Member..
thanks for your answer,
but where do i find the script in windows?
Does anybody know?

Regards
rainer
0 Likes
Highlighted
Absent Member.
Absent Member.
You will have to do this for each drive.

In Devices & Media select the drive.
Properties -> Settings -> Advanced -> Other

Here you can change from the default Delay of 30 minutes
and the script
C:\Program Files\OmniBack\bin\Mount.bat
to whatever is appropriate to your needs.

The default path may be different on your installation.
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..
in Devices & Media select the drive.
Properties -> Settings -> Advanced -> Other

Here you can change from the default Delay of 30 minutes
and the script
C:\Program Files\OmniBack\bin\Mount.bat
to whatever is appropriate to your needs.


Hi,
as i understand it, in the other i can change the default delay of 30 minutes. This is, the time until the mount script starts. What i want to change is the time, when the mount script aborts and gives the drive free for other tasks.
Actually it is waiting for several hours, while the other jobs are queuing and then time out. I woukd like to terminate this time but where?
0 Likes
Highlighted
Absent Member.
Absent Member.
Hi,

When the system detects the requirement for the mount it waits for the time specified in Delay. It then runs the script specified.

What you need to do is to change the Delay time to be 60 and change the script to one that will abort the backup instead.

I suggest that you make a copy of mount.bat and call it abort.bat and replace the last line with:

omniabort -session %SESSIONKEY%

Purists will say that you should put in the full path to omniabort but that should work.

Once this is in place you can change the script specified for the device(s) from mount.bat to abort.bat

Jeremy

View solution in original post

Highlighted
Absent Member.. Absent Member..
Absent Member..
Jeremy: this sounds good!
Probably, what Life wrote before with other words.

Thanks a lot

Rainer

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.