CASO - SSO and Library Expansion Issue
Hello all,
I have the following environment:
1x Tape library with one tape drive connected to a SAN.
3x Backup Exec Servers with the SSO license installed.
One of the three servers is configured with CASO option in order to administer the other Backup Exec Servers.
10x servers to backup with the appropriate licenses.
So, We have configured each server to backup some servers. All servers use (and see from the management console) the same library with the tape drive.
On the CASO server, I see the 2 other backup servers and in the device screen, i see 3 different devices. One for each server.
Every 30 mins I see an error in the alert screen about the Library expansion option. It says in a few words that we have license only for one device but it seems that more than one device is installed.
I have searched a little bit in Symantec and found that if I wan to share a tape drive, we should to install different Backup exec Servers with the SSO license to use the shared tape drive.
So my question is:
1. In order to avoid the error for the library expansion, I need to remove the caso option from the Central server and at the end to have three different individual servers. Correct?
2. With this topology, is there any option to have a centralized view of the backups?
PS. We inherited this topology from a previous installation. They used this topology in order to backup the servers directly from the SAN and not through the other servers, eg One backup server on the ORACLE server to backup itself directly to the tape, one server to the SQL server to backup directly itself to the tape and the last server on on DOMINO server (this is the central) to backup itself and some file servers directly to the tape drive.
Thanks in advance and sorry for the too much information!
I have the following environment:
1x Tape library with one tape drive connected to a SAN.
3x Backup Exec Servers with the SSO license installed.
One of the three servers is configured with CASO option in order to administer the other Backup Exec Servers.
10x servers to backup with the appropriate licenses.
So, We have configured each server to backup some servers. All servers use (and see from the management console) the same library with the tape drive.
On the CASO server, I see the 2 other backup servers and in the device screen, i see 3 different devices. One for each server.
Every 30 mins I see an error in the alert screen about the Library expansion option. It says in a few words that we have license only for one device but it seems that more than one device is installed.
I have searched a little bit in Symantec and found that if I wan to share a tape drive, we should to install different Backup exec Servers with the SSO license to use the shared tape drive.
So my question is:
1. In order to avoid the error for the library expansion, I need to remove the caso option from the Central server and at the end to have three different individual servers. Correct?
2. With this topology, is there any option to have a centralized view of the backups?
PS. We inherited this topology from a previous installation. They used this topology in order to backup the servers directly from the SAN and not through the other servers, eg One backup server on the ORACLE server to backup itself directly to the tape, one server to the SQL server to backup directly itself to the tape and the last server on on DOMINO server (this is the central) to backup itself and some file servers directly to the tape drive.
Thanks in advance and sorry for the too much information!
- Well, you'd install the SAN SSO option on your central server. This becomes your Primary server. This will hold the shared ADAMM and catalalog databases for the Shared Storage Network.
Any additional servers get installed as Secondary servers, and you will put in the name of your server of your Primary server. You can do this from the Install Options and License Keys on this Media Server on each distributed server.
Once done, the library will show up, and you can configure your jobs on those servers. These jobs will then show up on the Primary server.
In this case, I wouldn't use the CASO option if those distributed servers are backing other servers via an agent. You can report from the SAN SSO server.
