Backing up SQL Express

Hi everyone,
Can anyone tell me if tehre is a tool or some preffered means of backing
up SQL Express on a schedule.
I typically use SQL Agent to schedule backup jobs but SQL Express doesnt
seem to come with that.
Many thanks
Simon
What about doing a AT job within Windows with specifying something like
this as the command:
SQLCMD.EXE -S .\SQLExpress -Q -U Username -P Password -Q "BACKUP
DATABASE..."
HTH; Jens Suessmeyer.

Backing up SQL Express

Hi everyone,
Can anyone tell me if tehre is a tool or some preffered means of backing
up SQL Express on a schedule.
I typically use SQL Agent to schedule backup jobs but SQL Express doesnt
seem to come with that.
Many thanks
SimonWhat about doing a AT job within Windows with specifying something like
this as the command:
SQLCMD.EXE -S .\SQLExpress -Q -U Username -P Password -Q "BACKUP
DATABASE..."
HTH; Jens Suessmeyer.

Backing up SQL Express

Hi everyone,
Can anyone tell me if tehre is a tool or some preffered means of backing
up SQL Express on a schedule.
I typically use SQL Agent to schedule backup jobs but SQL Express doesnt
seem to come with that.
Many thanks
SimonWhat about doing a AT job within Windows with specifying something like
this as the command:
SQLCMD.EXE -S .\SQLExpress -Q -U Username -P Password -Q "BACKUP
DATABASE..."
HTH; Jens Suessmeyer.

backing up remote database

when I try to schedule a backup, or just do a backup, of a remote database
I get this error message:
"database 'msdb' cannot be opened. It has been marked SUSPECT by recovery."
I can connect to the database and view it.
I checked the error logs and there is no information about this error
listed.
I googled the error but did not find any solutions
Any insights to this error message ?
Answered in .programming
Please don't multi-post.
Regards
Mike
"TJS" wrote:

> when I try to schedule a backup, or just do a backup, of a remote database
> I get this error message:
> "database 'msdb' cannot be opened. It has been marked SUSPECT by recovery."
> I can connect to the database and view it.
> I checked the error logs and there is no information about this error
> listed.
> I googled the error but did not find any solutions
> Any insights to this error message ?
>
>

Backing up a DataBase

Hello:
I want to schedule a backup of a Database where a complete backup is done
keeping the Last 10 Complete BackUps Available at all times.
The Backup device file should be something like the DBName+SystemDateTime.
After 10days these backup files will be removed after being copied to
someother location and the whole process of starts all over again from
complete backup1 to complete back10..
Pls suggest some way of doing it.
Thank you.
Hi
The Maintenace Wizard works on this priciple. You define the backup
retention period, and after xx days, the oldest backup is deleted.
If you need to copy the backup off to another server, setup a seperate job,
using XCOPY
Regards
Mike
"Robin Chatterjee" wrote:

> Hello:
> I want to schedule a backup of a Database where a complete backup is done
> keeping the Last 10 Complete BackUps Available at all times.
> The Backup device file should be something like the DBName+SystemDateTime.
> After 10days these backup files will be removed after being copied to
> someother location and the whole process of starts all over again from
> complete backup1 to complete back10..
> Pls suggest some way of doing it.
>
> Thank you.
>

Backing up a DataBase

Hello:
I want to schedule a backup of a Database where a complete backup is done
keeping the Last 10 Complete BackUps Available at all times.
The Backup device file should be something like the DBName+SystemDateTime.
After 10days these backup files will be removed after being copied to
someother location and the whole process of starts all over again from
complete backup1 to complete back10..
Pls suggest some way of doing it.
Thank you.Hi
The Maintenace Wizard works on this priciple. You define the backup
retention period, and after xx days, the oldest backup is deleted.
If you need to copy the backup off to another server, setup a seperate job,
using XCOPY
Regards
Mike
"Robin Chatterjee" wrote:

> Hello:
> I want to schedule a backup of a Database where a complete backup is done
> keeping the Last 10 Complete BackUps Available at all times.
> The Backup device file should be something like the DBName+SystemDateTime.
> After 10days these backup files will be removed after being copied to
> someother location and the whole process of starts all over again from
> complete backup1 to complete back10..
> Pls suggest some way of doing it.
>
> Thank you.
>

Backing up a DataBase

Hello:
I want to schedule a backup of a Database where a complete backup is done
keeping the Last 10 Complete BackUps Available at all times.
The Backup device file should be something like the DBName+SystemDateTime.
After 10days these backup files will be removed after being copied to
someother location and the whole process of starts all over again from
complete backup1 to complete back10..
Pls suggest some way of doing it.
Thank you.Hi
The Maintenace Wizard works on this priciple. You define the backup
retention period, and after xx days, the oldest backup is deleted.
If you need to copy the backup off to another server, setup a seperate job,
using XCOPY
Regards
Mike
"Robin Chatterjee" wrote:
> Hello:
> I want to schedule a backup of a Database where a complete backup is done
> keeping the Last 10 Complete BackUps Available at all times.
> The Backup device file should be something like the DBName+SystemDateTime.
> After 10days these backup files will be removed after being copied to
> someother location and the whole process of starts all over again from
> complete backup1 to complete back10..
> Pls suggest some way of doing it.
>
> Thank you.
>sql

Back up File Location

I have created a schedule of transaction log backups, 1
every hour from 9am to 8pm with a differential back up
every 4 hours 1pm, 5pm and 9pm and full back ups once a
week. Under the advice of tech support the transaction log
backups should go to an area on another Server rather than
a tape. I want to try and keep the back up sets together,
so i will have a history of Full backup, Differential
backup and Transaction Log backs up in a single set. So i
want to use the same location for the Full and
differential backups. However tech support are going
bananas, saying that i shouldn't be moving so much data
accros the network. They can see that hourly transaction
logs should not be done to tape but are arguing that
weekly full backups should. The databases are not very big
in my eyes), a total of about 600mb and the full backups
run out of hours on a (sunday). As i said before, i would
like to have on backup set, not Full bacckups in one set
on tape and transaction log backups in another set on disk.
Any thoughts will be much appreciated as its me against
the world at the moment...Why not quite simply backup to disk and have those files picked up by your
tape software, like most of us are doing? :-)
For extra safety, you can add a job step which copies the backup file to
another machine directly after the backup is performed. (Personally, I don't
do the backup over the network if I can avoid. I prefer to backup locally
and copy the file after. If database size permits, of course.)
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"MAT" <anonymous@.discussions.microsoft.com> wrote in message
news:247501c3fc77$17ead6c0$a001280a@.phx.gbl...
> I have created a schedule of transaction log backups, 1
> every hour from 9am to 8pm with a differential back up
> every 4 hours 1pm, 5pm and 9pm and full back ups once a
> week. Under the advice of tech support the transaction log
> backups should go to an area on another Server rather than
> a tape. I want to try and keep the back up sets together,
> so i will have a history of Full backup, Differential
> backup and Transaction Log backs up in a single set. So i
> want to use the same location for the Full and
> differential backups. However tech support are going
> bananas, saying that i shouldn't be moving so much data
> accros the network. They can see that hourly transaction
> logs should not be done to tape but are arguing that
> weekly full backups should. The databases are not very big
> in my eyes), a total of about 600mb and the full backups
> run out of hours on a (sunday). As i said before, i would
> like to have on backup set, not Full bacckups in one set
> on tape and transaction log backups in another set on disk.
> Any thoughts will be much appreciated as its me against
> the world at the moment...
>|||Create a backup LAN between SQL server and backup destination server.
Backup on backup LAN IP address.
--
Nico De Greef
Belgium
Freelance Software Architect
MCP, MCSD, .NET certified
"MAT" <anonymous@.discussions.microsoft.com> wrote in message
news:247501c3fc77$17ead6c0$a001280a@.phx.gbl...
> I have created a schedule of transaction log backups, 1
> every hour from 9am to 8pm with a differential back up
> every 4 hours 1pm, 5pm and 9pm and full back ups once a
> week. Under the advice of tech support the transaction log
> backups should go to an area on another Server rather than
> a tape. I want to try and keep the back up sets together,
> so i will have a history of Full backup, Differential
> backup and Transaction Log backs up in a single set. So i
> want to use the same location for the Full and
> differential backups. However tech support are going
> bananas, saying that i shouldn't be moving so much data
> accros the network. They can see that hourly transaction
> logs should not be done to tape but are arguing that
> weekly full backups should. The databases are not very big
> in my eyes), a total of about 600mb and the full backups
> run out of hours on a (sunday). As i said before, i would
> like to have on backup set, not Full bacckups in one set
> on tape and transaction log backups in another set on disk.
> Any thoughts will be much appreciated as its me against
> the world at the moment...
>