cancel
Showing results for 
Search instead for 
Did you mean: 

SYMBDSNAP

tanyshka
Level 3

Hello,

I am using RHEL 4.9.

I installed an agent Backup Execk 2012: RALUS_RMALS_RAMS-1798.17.tar.gz
Then I noticed the error in log file /var/log/messages:
 
SYMBDSNAP_SDK[29044]: Failed to open device: /dev/symbdsnapctl, errno: 2.
 
 
What does it mean?
18 REPLIES 18

VJware
Level 6
Employee Accredited Certified

Maybe due to the fact, BE 2012 does not support RHEL 4.x...It supports only 5.x & 6.x

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

VJware is corect - just for info the symbdsnap driver is the Open File Manager for RALUS in BE 2012 and is very limited on what operating systems it is supported on.

tanyshka
Level 3

Thank you for your reply.

Amarnath_Sathis
Level 5

Please check the OS, Software and Hardware Compatibility Guide before trying to install BE.

Ken_Putnam
Level 6

Already mentioned last week

teekay78
Level 2
# cat /etc/*release
Red Hat Enterprise Linux Server release 6.2 (Santiago)
# grep SYMBDSNAP /var/log/messages
Jul 11 10:41:50 phbuild02 SYMBDSNAP_SDK[17961]: Failed to open device: /dev/symbdsnapctl, errno: 2.
Jul 11 10:41:50 phbuild02 SYMBDSNAP_SDK[17961]: Failed to open device: /dev/symbdsnapctl, errno: 2.
Jul 11 11:43:09 phbuild02 SYMBDSNAP_SDK[17961]: Failed to open device: /dev/symbdsnapctl, errno: 2.

We also do run RHEL 5.4 where it works fine, and some other RHEL 5.4 where it spits the same issue as shown above - all with default RHEL kernels.

So, what does it mean?

criley
Moderator
Moderator
Employee Accredited

Have you confirmed that you are running a supported file system?

Advanced Open File Option for Linux is supported. (only for Ext 2, Ext 3, Ext 4, Reiser FS file systems)

Is this error causing backups to fail?

SUV-BE
Level 2
Employee

Hi teekay78,

Are you sure you noticed this for RHEL 5.4 ? Looks like you are trying snapshot on RHEL 6.2 (Not yet supported by Backup Exec 2012)?

# cat /etc/*release
Red Hat Enterprise Linux Server release 6.2 (Santiago)

If you noticed this on RHEL 5.4 can you send your full /var/log/messages ?

DominikG
Level 6
Partner Accredited

Hi,

any update regarding this issue?
Currently got a customer with the same error messages on supported Linux systems.

 

teekay78
Level 2

The RHEL 5.4 machines use EXT3, the 6.2 ones EXT4 - RHEL defaults that is.

Backups do not fail fortunately.

criley
Moderator
Moderator
Employee Accredited

Dominik,

If you are seeing this issue on a supported OS with supported file system, I would recommend you open a support case.

teekay78
Level 2

The logs from the affected 5.4 machine isn't very verbose:

 

Sep 12 21:34:56 phsysint01 SYMBDSNAP_SDK[18085]: Failed to open device: /dev/symbdsnapctl, errno: 2. 
Sep 12 21:34:56 phsysint01 last message repeated 5 times

The other affected 5.4 machine got replaced by a 6.2 VM two weeks ago.

VJware
Level 6
Employee Accredited Certified

symdbsnap was introduced in BE 2012 & thats the reason as to why the this message was not seen with earlier versions of BE...

Backup would still run fine, however if you see this message, then most probably, the open files were not backed up (symdbsnap is responsible here for the open files backup)..

Martinus-Apo
Level 3

We have the same message on a NOT supported "Debian 6.0.5" 64bit machine after we upgraded the RALUS agent to the version needed for BackupExec2012. We did not have this message with the RALUS agent for BackupExec 12.5.

The backup jobs work fine though. It's just the message which appears in syslog. Is there no workaround for this problem? Maybe some symbolic links if I would know the target?? What is the purpose of this device anyway??

tanyshka
Level 3

Try to restore from this backup. I did not recover the data.

criley
Moderator
Moderator
Employee Accredited

Not sure exactly what you mean. Can you provide more details?

This module is for AOFO only. A workaround is to disable it.

The issue needs further investigation so please open a case with support.

tanyshka
Level 3

I have contacted the support, it did not help.

criley
Moderator
Moderator
Employee Accredited

What is the case id?

Your original post mentions RHEL 4.9 which is not supported with BE 2012.

Are you seeing the issue with supported versions of Linux?