Debian Linux and Commvault Simpana 9 startup

If you’ve recently installed Commvault Simpana 9 software/services onto a Debian Linux client, be sure check your runlevel and ensure that the software/services will start on the next reboot automatically.

By default simpana 9 software/services will be linked into runlevel 3 and runlevel 5, however on Debian the default runlevel is 2. (When your not running any X11 that is).

To confirm what runlevel the system runs by default you can check the inittab file and confirm an entry. Below is an example;

root@ldebx86-1:~# cat /etc/inittab | grep initdefault
id:2:initdefault:

And the same output from a CentOS 5.6 server (which is running X windows);

[root@lcosx86v56-1 ~]# cat /etc/inittab | grep initdefault
# 0 – halt (Do NOT set initdefault to this)
# 6 – reboot (Do NOT set initdefault to this)
id:5:initdefault:

From the output we can see that the top most one will default to runlevel 2 and the bottom one runlevel 5.

If you cat the inittab file you will see some comments indicating the runlevels;

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

And from CentOS 5.6 server;

# Default runlevel. The runlevels used by RHS are:
# 0 – halt (Do NOT set initdefault to this)
# 1 – Single user mode
# 2 – Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 – Full multiuser mode
# 4 – unused
# 5 – X11
# 6 – reboot (Do NOT set initdefault to this)
#

Post my Commvault Simpana 9 Linux File System iDA deployment, we go check for the Galaxy initscript being linked from the runlevel directories, and as you can see below, no script for runlevel 2, thus these services will not come up automaticaly upon reboot on this server.

root@ldebx86-1:/etc/rc3.d# ls -l *Galaxy*
lrwxrwxrwx 1 root root 16 Apr 8 19:07 S23Galaxy -> ../init.d/Galaxy
root@ldebx86-1:/etc/rc3.d# cd ..
root@ldebx86-1:/etc# cd rc2.d
root@ldebx86-1:/etc/rc2.d# ls -l *Galaxy*
ls: cannot access *Galaxy*: No such file or directory
root@ldebx86-1:/etc/rc2.d#

This can be resolved by of course creating the same symlink in the runlevel 2 directory and it will work next time as expected.

cd /etc/rc2.d
ln -s ../init.d/Galaxy S23Galaxy

Now we check again to confirm it created;

root@ldebx86-1:/etc/rc2.d# ls -l *Galaxy*
lrwxrwxrwx 1 root root 16 Apr 8 19:15 S23Galaxy -> ../init.d/Galaxy

Job done.