Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Device Configuration Guide
  3. Section I. Operating systems
  4. Solaris
  5. Installing/reinstalling the sg and the st drivers
  6. sg.links file example
Veritas NetBackup™ Device Configuration Guide

sg.links file example

The following /usr/openv/volmgr/bin/driver/sg.links file example shows targets 0-15 and LUNs 0-7. It also includes entries for three StorEdge Network Foundation HBA ports.

The sg.build -mt option does not affect FCP targets, but the -ml option does. The Solaris luxadm command detected three ports (identified by their World Wide Names). Therefore, the sg.build script created entries for LUNs 0 through 7 for those three ports.

The field separator between the addr=x, y; field and the sg/ field is a tab. The addr= field uses hexadecimal notation, and the sg/ field uses decimal values.

# begin SCSA Generic devlinks file - creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0;       sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=0,1;       sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=0,2;       sg/c\N0t0l2
type=ddi_pseudo;name=sg;addr=0,3;       sg/c\N0t0l3
type=ddi_pseudo;name=sg;addr=0,4;       sg/c\N0t0l4
type=ddi_pseudo;name=sg;addr=0,5;       sg/c\N0t0l5
type=ddi_pseudo;name=sg;addr=0,6;       sg/c\N0t0l6
type=ddi_pseudo;name=sg;addr=0,7;       sg/c\N0t0l7
type=ddi_pseudo;name=sg;addr=1,0;       sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=1,1;       sg/c\N0t1l1
...
<entries omitted for brevity>
...
type=ddi_pseudo;name=sg;addr=f,5;       sg/c\N0t15l5
type=ddi_pseudo;name=sg;addr=f,6;       sg/c\N0t15l6
type=ddi_pseudo;name=sg;addr=f,7;       sg/c\N0t15l7
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c3,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c6,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53c9,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53cc,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f0008d53b9,1;       sg/c\N0t\A1l1
# end SCSA devlinks

Feedback

Was this page helpful?
Previous

sg.conf file example

Next

Configuring 6 GB and larger SAS HBAs in Solaris

Feedback

Was this page helpful?