Be10d for SQL server

[Frode_Simonsen]

 Hi Guys,
I have a customer which has a 1x Windows 2003 server and uses SQL server, but only one database and about 5 users using it.  Would I need the backup exec SQL agent as well has Backup Exec 10d for Windows server.
And is there a cheap why off backing up the server and the SQL database?? 

Cheers,
Frode

[Dev_T]

Hello,

You need a BE SQL Agent for Backing up SQL Database. If you do want to purchase an agent you can take the SQL Databases OFFLINE and Backup SQL database as FLAT FILES. You will require Remote Agent for Windows Server License for this.

Hope this helps./...

[pkh]

10d is quite old.  If you are thinking of buying BE, you should go for the latest version which is 2010.

You will need both BE and the BE SQL agent to backup the SQL database.  It is not advisable to just backup the .mdf and the .ldf files because they would be just snapshots of the database.

The only cheap way to backup your system is to use the native SQL Server backup and ntbackup.

[Carls · Accepted solution]

 If you need to backup the database while it is online, you'd need the agent for sql server, yes. SQL also has some commands (you'd have to look for them) with which you can dump the database to backup files, and these you can just backup because once the dump is done the files aren't open anymore. In the case of a disaster you'd have to import these files back into the database. It is advisable that you use such dumps in anycase, and to another HD than where your database resides on. You can run these dumps in short intervalls which would ensure that in case of the database going corrupt you'd have a better chance of restoring all your data.

Carl

[Hobbs]

 Frode,
In SQL, you can create a maintenance plan that includes backing up of the database. You are then able to restore the database using these backups.

Once you've got a backup of your SQL database, then use NTbackup and include the folder locations where your SQL maintenance plan has saved the backups.

In the above scenario you would not need to use SQL server agent.

P.S. Bearing in mind that most W2K3 server have shadow copy installed it is recommended that you not include the location of the actual files being used in the database. These files will also be included in yourbackup. Although it is not recommended that your actual database files are included in the NTbackups.

Ben

[Amith]

 Hi Frode,
You can always use a trick - if your databases can spare a little downtime - setup a pre and postbackup script (command really) - the pre:

NET STOP MSSQLSERVER

The post backup:

NET START MSSQLSERVER

This will STOP the SQL Server service, allowing the backup software to backup the file like any other, then start the SQL service after the backup has begun. 

In the case of a restore, you would have to detach the existing database and then attach the restoredbackup files (LOG (LDF) AND MDF).

Though honestly, I'd probably do the SQL based backup to a file otherwise.

Amith

[Ken_Putnam]

You can always use a trick - if your databases can spare a little downtime - setup a pre and postbackup script (command really) - the pre:

NET STOP MSSQLSERVER

The post backup:

NET START MSSQLSERVER

If you are going to recommend this you need to include directions on how to disable AFE

http://seer.entsupport.symantec.com/docs/259152.htm

since even with the SQL Server service stopped, Active File Exclusion will still skip the database files