Sun Enterprise 4000 Server
 
Solstice Backup (SBU) Software
 
Solaris SPARC Operating System
 

GCS>Sun Microsystems>Servers>Midrange Servers
 

It is possible to workaround this problem IF the system has 2 or more
network interfaces.  This will not work with less than 2 network
interfaces.
NOTE: SBU 4.2.2 version of /usr/sbin/nsr/save does not support the -c
option. SBU 4.2.6 does. A save binary that supports the -c flag for
SBU 4.2.2 is available via anonymous ftp to: deimos.central under
pub/networker/4.2.2 and it is called save-c.gz. There is a utility
to unzip this under pub/networker/bin called gunzip.
To use this, copy both files to your system and run:
# gunzip save-c.gz
This will create a file called save-c.
# mv /usr/sbin/nsr/save /usr/sbin/nsr/save.orig
# cp save-c /usr/sbin/nsr/save
# chown root /usr/sbin/nsr/save
# chmod u+s /usr/sbin/nsr/save
1) This example was run on a system called e4000 running Solaris[TM] 2.5.1
and Solstice Backup 4.2.2, there are 2 hme interfaces (hme0 and hme1).
2) The /etc/hosts file should resemble:
#
# Internet host table
#
127.0.0.1       localhost
129.151.35.25   e4000      loghost
129.151.35.35   e4000-gw
3) Create the files hostname.hme0 and hostname.hme1:
# more /etc/hostname.hme0
e4000
# more /etc/hostname.hme1
e4000-gw
4) Create 2 scripts under /usr/sbin/nsr that begin with a save prefix:
# vi /usr/sbin/nsr/save.e4000
#!/bin/sh
echo "Starting Backup"
exec /usr/sbin/nsr/save -c e4000 $@
echo "Backup Complete"
exit
# vi /usr/sbin/nsr/save.e4000gw
#!/bin/sh
echo "Starting Backup"
exec /usr/sbin/nsr/save -c e4000-gw $@
echo "Backup Complete"
exit
5) Run chown root on each of the scripts.
6) Run chmod 777 on each of the scripts.
7) Then bring up the nwadmin gui and click on client and then client
setup.
8) Create a client called e4000 and chose a schedule, browse and
retention policies, directives, a group, and the savesets needed
by this client to backup. (These savesets should be different than
the 2nd clients savesets).
9) In the remote access field type:
*@e4000
10) In the Backup Command field type:
save.e4000
11) And then click on apply.
12) Then create a 2nd client called e4000-gw.  Again choose a
schedule, browse policy, retention policy, directive, and
savesets (which differ from the first client).
13) In the remote access field type:
*@e4000
14) In the backup command field type:
save.e4000gw
15) And then click on apply.
16) Shutdown the daemons with /etc/init.d/networker stop
and start them up again with /etc/init.d/networker start.
17) Go to group control and click on the group to be backed up
(I added both clients to the same group) and click on start
to start a backup immediately (this step is optional).
18) After completion cd to /nsr/index and ls displays:
# cd /nsr/index
# ls
e4000     e4000-gw
cd to e4000 and verify:
# ls -lsa
total 570
2 drwxr-xr-x   2 root     other        512 Jul 17 14:54 .
2 drwxr-xr-x   4 root     other        512 Jul 17 14:18 ..
2 -rw-r--r--   1 root     other         32 Jul 17 14:54 .nsr
4 -rw-r--r--   1 root     other       1901 Jul 17 14:54 README
560 -rw-------   1 root     other    2637824 Jul 17 15:13 db
cd to e4000-gw and verify:
total 426
2 drwxr-xr-x   2 root     other        512 Jul 17 15:11 .
2 drwxr-xr-x   4 root     other        512 Jul 17 14:18 ..
2 -rw-r--r--   1 root     other         32 Jul 17 15:11 .nsr
4 -rw-r--r--   1 root     other       1901 Jul 17 15:11 README
416 -rw-------   1 root     other    2239884 Jul 17 15:11 db
The backups for the 2 clients (same system) are going to 2 separate
databases.  If there were more network interfaces on the system then
more client entries could be created.

This solution has no attachment