sims backup

[arthur231283]

I am using Symantec Backup exec 11d and have the agent for SQL Server 2000. The sims server seems to be backing up fine including the SQL but it is not backing up the sims.ldf, sims.mdf, ccsfms.ldf and ccsfms.mdf files. I have looked on the symantec support pages but have not found anything.

 

Is there a setting or a tick box some where that I need to change to get these files to backup?

or is there a different way I should be backing up these files?

[Richie1972]

That sounds like you've not got the Open Files backup module for BackupExec

[synaesthesia]

Was about to say some naughty user's keeping their SIMS logged in at the time you're backing up - but "open files module" ? Interested

[FN-GM]

I have a script that forces reboots every computer in school before the backups. Saves problems like this....

[Steve_T]

SQL stop/start batch files, do you have them?

[matt40k]

Like Steve said, stop MSSQL

 

Or get the Symantec SQL addin

 

Or scheduled dbattach to backup SIMS, then exclude the .mdf\.ldf (MSSQL data folder)

[IrritableTech]

As others have said, you'll need to either run a script scheduled or run a pre-job / post-job command on the job.

 

It would be along these lines

 

NET STOP MSSQL$SIMS2005

 

and afterwards

 

NET START MSSQL$SIMS2005

[Mcshammer_dj]

You can use Dbattach to backup the SIMS database via a scheduled task

 

there are various switches that make this simple to do

 

in your first statement you mention the SQL agent for SQL2000?? Sims should be on SQL 2005

Edited April 29, 2009 by Mcshammer_dj

[arthur231283]

Thanks for all the suggestions I do have the Agent for SQL and I have installed the open files backup module on the server. I have checked that I have selected the files in the backup selection list but its still not backing up the sims.ldf/.mdf and ccsfms.ldf/.mdf files. So it looks like I will need to create the batch file to stop and start the SQL.

[Mcshammer_dj]

You shouldn't need a batch file as Backup exec has the functionality to stop services as required.

[westleya]

Thanks for all the suggestions I do have the Agent for SQL and I have installed the open files backup module on the server. I have checked that I have selected the files in the backup selection list but its still not backing up the sims.ldf/.mdf and ccsfms.ldf/.mdf files. So it looks like I will need to create the batch file to stop and start the SQL.

 

Was this ever resolved ? I have EXACTLY the same problem with Backup Exec 11d and SIMS....

[matt40k]

There is two backupExec addons

 

One is open files, the other is MSSQL (2005 NOT MSDE\2000). You need the MSSQL to backup SIMS, the open files can't backup .mdf\.ldf. Both addins are extras.

 

OK not call addons but AGENTS.

 

Symantec Backup Exec for Windows Servers: Agents & Options - Symantec Corp.

 

(Yes, I know v.12 but v.10 is the same licensing model (almost))

Edited May 12, 2009 by matt40k

[Steve_T]

Create two batch files as follows as save them somewhere C:\XXXX\XX.bat,

 

@echo off

net start "MSSQL$SIMS"

 

@echo off

net stop "MSSQL$SIMS"

 

Note: instance name may be different.

 

Doing this blind so forgive me if this is wrong.

 

Job Monitor - Right click on backup - properties - pre and post commands - type location of the above files you have created - leave default settings - test.

[Oops_my_bad]

Is it safe to stop/start the SQL instance before taking a backup of the SQL database(s)? I was always under the impression you should be doing all backups through dbAttach (or some other method such as BE)

[matt40k]

Is it safe to stop/start the SQL instance before taking a backup of the SQL database(s)? I was always under the impression you should be doing all backups through dbAttach (or some other method such as BE)

 

You'll need to have SQL running to use dbAttach as it does a live backup.

[wesleyw]

A live backup is what Backup Exec is doing you won't find the files but you should be able to restore the dbs to another sql server you just have to specify which during the restore. As for SQL Server backups these are much better tbh..

 

Wes

[matt40k]

Only if you have the agent! Which is like £100.

[wesleyw]

I am using Symantec Backup exec 11d and have the agent for SQL Server 2000.

 

He has got the SQL Server Agent?

 

Wes

[meastaugh1]

I am using Symantec Backup exec 11d and have the agent for SQL Server 2000. The sims server seems to be backing up fine including the SQL but it is not backing up the sims.ldf, sims.mdf, ccsfms.ldf and ccsfms.mdf files. I have looked on the symantec support pages but have not found anything.

 

Is there a setting or a tick box some where that I need to change to get these files to backup?

or is there a different way I should be backing up these files?

 

I didn't think you should expect to see the live database files as flat files in the backup, even when you have the SQL agent. I believe you should see the SQL instances and databases available to backup/restore as a separate node, similar to how AD and system state are represented.

 

Is it safe to stop/start the SQL instance before taking a backup of the SQL database(s)? I was always under the impression you should be doing all backups through dbAttach (or some other method such as BE)

 

I use dbattach as the primary backup method and the BE SQL agent as secondary. The only SQL services we used to stop/start were the SQL Anywhere services for FMS.

[Steve_T]

@ECHO OFF

COLOR CF

ECHO YOUR SQL DATABASE IS CURRENTLY BEING BACKED UP, THIS MAY TAKE SEVERAL MINUTES

DBATTACH /BACKUP /AUTO /SERVER=XXXXX\SIMS2005 /user=sa /password=XXXXXX /DATABASE=sims

DBATTACH /BACKUP /AUTO /SERVER=XXXXX\SIMS2005 /user=sa /password=XXXXXX /DATABASE=ccsfms

 

Schedule that and mark the backup folderfor SQL in your Agents selections so you have both

[sahmeepee]

Be careful if you do it this way. As you're not doing a 'proper' backup (as far as SQL server is concerned), the log file is never truncated or shrunk. If you don't backup using either an SQL backup task or a backup agent, the log files will grow to humongous sizes. The log file is not truncated until SQL server is sure that the database has been backed up.

 

It's always best to use some proper backup solution.

 

That said, dbattach (in a batch similar to Steve_T's above) is a Capita-recommended method for your nightly backups. We have been using it for a good while and have never had problems with transaction logs growing. I suspect either: dbattach takes care of the problem -or- the SQL backup which happens before every upgrade or database patch is frequent enough to remove the problem.