Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 340
  • Last Modified:

Backup Exec 10d

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,
Johno

0
davidalley
Asked:
davidalley
2 Solutions
 
rindiCommented:
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 as I don't know 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.
0
 
Leon FesterIT Project Change ManagerCommented:
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 your backup. Although it is not recommended that your actual database files are included in the NTbackups.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
You can always use a trick - if your databases can spare a little downtime - setup a pre and post backup 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 restored backup files (LOG (LDF) AND MDF).

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

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now