cancel
Showing results for 
Search instead for 
Did you mean: 

Debian 8.3 and BackupExec 15FP3

slawek
Level 3

Hello

 

According to SCL onlu Debian 8.0 is supported - that I know.

Is anyone has Debian 8.3 with working RALUS agent on it?

According to logs

root@cod:~# service VRTSralus.init status
● VRTSralus.init.service - LSB: Symantec Backup Exec Remote Agent
   Loaded: loaded (/etc/init.d/VRTSralus.init)
   Active: active (running) since Wed 2016-02-24 10:03:39 CET; 3min 34s ago
  Process: 23966 ExecStart=/etc/init.d/VRTSralus.init start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/VRTSralus.init.service
           └─23973 /opt/VRTSralus/bin/beremote

Feb 24 10:03:34 cod SYMBDSNAP_SDK[23973]: Driver is not loaded. Loading symbdsnap.
Feb 24 10:03:34 cod SYMBDSNAP_SDK[23973]: Missing symbdsnap driver.
Feb 24 10:03:34 cod SYMBDSNAP_SDK[23973]: Failed to open device: /dev/symbdsnapctl, errno: 2.
Feb 24 10:03:34 cod SYMBDSNAP_SDK[23973]: Driver is not loaded. Loading symbdsnap.
Feb 24 10:03:34 cod SYMBDSNAP_SDK[23973]: Missing symbdsnap driver.
Feb 24 10:03:34 cod SYMBDSNAP_SDK[23973]: Failed to open device: /dev/symbdsnapctl, errno: 2.
Feb 24 10:03:39 cod VRTSralus.init[23966]: Starting Symantec Backup Exec Remote Agent ......
Feb 24 10:03:39 cod VRTSralus.init[23966]: Starting Symantec Backup Exec Remote Agent:                              [  OK  ]
root@cod:~#

everything seems to be ok - this problem is reported in https://www.veritas.com/support/en_US/article.000018862

But my problem is that I can't add this serwer to backupexec console.

 

Regards

Slawek

1 ACCEPTED SOLUTION

Accepted Solutions

pkh
Moderator
Moderator
   VIP    Certified
You can't add the server to the BE console because that version of Debian is not supported

View solution in original post

2 REPLIES 2

pkh
Moderator
Moderator
   VIP    Certified
You can't add the server to the BE console because that version of Debian is not supported

slawek
Level 3

OK - but qustion is - is it a workaround that will allow that?

I remember same situation with kernel 3.xx - there was a fix for that.

 

Regards

Slawek