BE 11d and SQL logging? 2

[pinkpanther56]

I have recently installed BE11d and have after some effort got it working with our SQL 2000 server which is installed on the same box.

I will shortly be installing BE11d on a second server and would like it to log to the SQL server as well are there any issues with allowing it to use the same instance and Db as another install of BE?

We will eventually have 3 servers running BE11d and i would like all of them to log to the same SQL server.

Thanks.

 

[steveot]

No its not possible unless your running SAN/SSO option.

Three media server can share the same BEDB database in a SQL server.

There is no way for them to keep track of media, resource, etc.

 

[pinkpanther56]

Hi steveot thanks for the reply, could you give me an idea of the best way to install for my setup.

We have:

4 x Windows 2003 servers to backup

Server 1: runs Windows 2003 with SQL 2000, this is the server that i have installed BE on currently and is backing up to it's own tape drive and logging to the SQL server.

Server 2: has it's own tape drive as well i have another BE licence for this and would like it to backup to it's tape drive but log to the SQL server on Server 1.

Server 3: this server is identical to server 2 and i would like it to do the same.

Server 4: i have a remote agent for this server and i would like server 2 to back this server up as it has a 200Gb LTO drive.

I would appreciate any input on how i can set this up correctly, as we have a full SQL server i'm hoping to avoid using MSDE locally as 2 of the servers are DC's.

Thanks.

 

[pinkpanther56]

Oh the 3 servers will have their own independant media sets.

I'm sorry if i'm not making sence i have a background in ARCServe and haven't had to use SQL server for this before.

 

[steveot]

Are you loooking to manage everything from one console?

Other that that Just install Backup Exec individually on Server 1,2,3. Each install will install a local copy of SQL 2005 express on each machine. There is no way around this. Yes you could tell backup exec to intall into a sql instance on another server but it all three cant be pointing to the same instance.

NOW..you can purchase the CASO Central Admin Server option which nothing changes. It still installs SQL locally but there is a link in the database that can point to one server. You make server 1 the central admin server. Then you make server 2,3 managed media server. Basically you logon to server 1 and create all jobs there and media sets, then then delegate tell the jobs to run on the desired media server. Basically you only have to logon to server1 day to check the status of all the job between the three server. You will see all jobs for each server in the job setup/monitor/history for all server.

 

[pinkpanther56]

Typical it sounds like we we're told incorectly by Symantec, we spacifically said that we didn't want to have SQL express running on every server especially our DC's they said that as we had full SQL it wouldn't be an issue.

Is the CASO an expensive extra componant?

So if i made server 1 with SQL 2000 on an Admin server i would be able to set us up as required?

Thanks.

 

[steveot]

No, each servers need SQL installed on it period.... or it need to be pointed to a instance on another server but the server cannot share the same instance of backup exec. You cant mount three BEDB database name into one sql instance..you cant do this with any sql database or in sql.

What support may have told you is that when you install backup exec that yes you dont have to install SQL locally and you can point the install to a remote sever running SQL..this is a true statement. You cant however install server1 and pointe it to SQLserver1, then install server2 and point it to sqlserver1. There is no way the install will let you and this would not be possible in sql two have BEDB database name listed twice. Now..if on you sql server if you installed sql 3 time with three different instance name (bkupexec1,bkupexec2,bkupexec3) then that would work. When you install Backup Exec on server1 point it to sqlserver1\bkupexec1, when you install backup exec on server2 point it to sqlserver1\bkupexec2, etc

But with the scenerio I just mentioned you would logon to each media server and create the job locally..so you would be manageing 3 media server. CASO will only add the benifit of being able to manage all three from one media server.

CASO i think its around $1k if I remember.

 

[pinkpanther56]

Ok i'm with you now i was hoping there might be an option to name the BE Db during install so you could have BEDb1 BEdb2 and BEDb3 all on the same instance, i see now that i was barking up the wrong tree.

Thanks.

 

[pinkpanther56]

Sorry to drag this back up.

The media server isn't an option so it looks like MSDE on each server, does this pose any security or performance problems?

Thanks.

 

[Zelandakh]

Nope, just download it.

 

[pinkpanther56]

Hi

Even on a domain controller i've read about performance issues with it consuming memory or is this just an a busy MSDE server?

Thanks.

 

[Zelandakh]

If you aren't already overloading a server, MSDE will be fine.