Issues with startup order

English Install/Boot/Login
#1

I have a server running OpenSUSE 12.1 I also have an iSCSI array attached that is used for primary backup, and this mounts as /media/Drobo1. I have backup software running on both this system and several networked workstations that automatically back up to this location.

When I start up, my backup software tries to back up before the iSCSI drive is up, and creates a new Drobo1 folder in /media. When the iSCSI array mounts it creates a new name, such as Drobo1_1 and the backups go to the newly-created Drobo1 folder instead. At this point I must manually shut down the backups, unmount the array, delete the newly-created Drobo1 folder, then remount the array and restart the backups.

Oh, BTW, when I upgraded from 11.4 to 12.1, eth1, the iSCSI connection, somehow became br0, a bridge connection.

Does anyone know how I can either prevent a new folder from being created in /media before the array is mounted, or change the load order as follows:

  1. Load br0 (or eth1 if I have to change it back). This is the connection for the iSCSI array.
  2. Load the iSCSI client.
    3, Load eth0.
  3. Load the server instance of the backup software.

Thanks in advance for any help.

Any help would be appreciated.

#2

On 2013-05-13 20:16, corrigan wrote:
>
> I have a server running OpenSUSE 12.1 I also have an iSCSI array
> attached that is used for primary backup, and this mounts as
> /media/Drobo1. I have backup software running on both this system and
> several networked workstations that automatically back up to this
> location.

Why does it mount there? Is it external? Does it have entries in fstab?

> When I start up, my backup software tries to back up before the iSCSI
> drive is up, and creates a new Drobo1 folder in /media. When the iSCSI
> array mounts it creates a new name, such as Drobo1_1 and the backups go
> to the newly-created Drobo1 folder instead. At this point I must
> manually shut down the backups, unmount the array, delete the
> newly-created Drobo1 folder, then remount the array and restart the
> backups.

How is that backup software started? What is it?

If it is a script, I would modify it.
If it is not, I would write a script that calls that unnamed backup
software.

The script simply has to verify that the mount is available, and if not,
wait. After some time of waiting unsuccessfully, alert the operator and
probably abort.

> Oh, BTW, when I upgraded from 11.4 to 12.1, eth1, the iSCSI connection,
> somehow became br0, a bridge connection.

Mmm.

> Does anyone know how I can either prevent a new folder from being
> created in /media before the array is mounted, or change the load order
> as follows:

Change load order, no. That’s why methods exist to get permanent names
for disk devices.

> 1. Load br0 (or eth1 if I have to change it back). This is the
> connection for the iSCSI array.
> 2. Load the iSCSI client.
> 3, Load eth0.
> 4. Load the server instance of the backup software.

Hold on, that array is mounted over the network, via nfs or something?
Why in /media?

You are not explaining all.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)