Backing up SQL to a different server

I am trying to send backups of SQL databases and
transaction logs to a different server. I thought it
would work if the UNC name and path were used. So, first
of all, I don't if this is correct. I think it's trying
to do the backup, but the error I am getting
is "BackupDeviceFile::Backup device "\\erlfs1
\sqlbackups\..." failed to create. Operating system error
=5 (Access is denied.)" I have given the Everyone group
full control, and I still get the same error. Does anyone
have recommendations for sending backups to a different
machine?Make sure you are running SQL under a domain-level account and that the
account has permissions to create and write files on the remote location.
Logging in to the console of the SQL server as the service account and
copying files is a good way to test remote file access.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"teresa" <anonymous@.discussions.microsoft.com> wrote in message
news:1454601c3c33c$58da9540$a601280a@.phx.gbl...
> I am trying to send backups of SQL databases and
> transaction logs to a different server. I thought it
> would work if the UNC name and path were used. So, first
> of all, I don't if this is correct. I think it's trying
> to do the backup, but the error I am getting
> is "BackupDeviceFile::Backup device "\\erlfs1
> \sqlbackups\..." failed to create. Operating system error
> =5 (Access is denied.)" I have given the Everyone group
> full control, and I still get the same error. Does anyone
> have recommendations for sending backups to a different
> machine?|||The SQL server is logged in under the domain admin account
and the domain admin has full control on the remote folder
that SQL is trying to back up to. Also, SQL Server Agent
service is started under the domain admin account and the
particular job is owned by the domain admin. I was able
to copy a file from the console to the backup server.
Looking at the event viewer, after a job has failed, one
error says "operating system eror = 5 (access is denied),"
another one says that the job failed and that it was
invoked by user 'sa'. I mention this because I don't
if 'sa' trying to invoke the job is the problem.
>--Original Message--
>Make sure you are running SQL under a domain-level
account and that the
>account has permissions to create and write files on the
remote location.
>Logging in to the console of the SQL server as the
service account and
>copying files is a good way to test remote file access.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>
>"teresa" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1454601c3c33c$58da9540$a601280a@.phx.gbl...
>> I am trying to send backups of SQL databases and
>> transaction logs to a different server. I thought it
>> would work if the UNC name and path were used. So,
first
>> of all, I don't if this is correct. I think it's trying
>> to do the backup, but the error I am getting
>> is "BackupDeviceFile::Backup device "\\erlfs1
>> \sqlbackups\..." failed to create. Operating system
error
>> =5 (Access is denied.)" I have given the Everyone group
>> full control, and I still get the same error. Does
anyone
>> have recommendations for sending backups to a different
>> machine?
>
>.
>|||Ping the second server from the first using UNC (ping
Servername). If you can not ping, use the IP address (To
find IP...Ipconfig).
Second Check the the 'Domain Admins' group is added
to 'Administrators' group of the second server.
>--Original Message--
>The SQL server is logged in under the domain admin
account
>and the domain admin has full control on the remote
folder
>that SQL is trying to back up to. Also, SQL Server Agent
>service is started under the domain admin account and the
>particular job is owned by the domain admin. I was able
>to copy a file from the console to the backup server.
>Looking at the event viewer, after a job has failed, one
>error says "operating system eror = 5 (access is
denied),"
>another one says that the job failed and that it was
>invoked by user 'sa'. I mention this because I don't
>if 'sa' trying to invoke the job is the problem.
>>--Original Message--
>>Make sure you are running SQL under a domain-level
>account and that the
>>account has permissions to create and write files on the
>remote location.
>>Logging in to the console of the SQL server as the
>service account and
>>copying files is a good way to test remote file access.
>>--
>>Geoff N. Hiten
>>Microsoft SQL Server MVP
>>Senior Database Administrator
>>Careerbuilder.com
>>
>>"teresa" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:1454601c3c33c$58da9540$a601280a@.phx.gbl...
>> I am trying to send backups of SQL databases and
>> transaction logs to a different server. I thought it
>> would work if the UNC name and path were used. So,
>first
>> of all, I don't if this is correct. I think it's
trying
>> to do the backup, but the error I am getting
>> is "BackupDeviceFile::Backup device "\\erlfs1
>> \sqlbackups\..." failed to create. Operating system
>error
>> =5 (Access is denied.)" I have given the Everyone
group
>> full control, and I still get the same error. Does
>anyone
>> have recommendations for sending backups to a different
>> machine?
>>
>>.
>.
>sql

Backing up SQL Databases

Hello:
How do you change the scheduled database backups in SQL Server 2000?
We have a scheduled backup of a production database that is run once a day.
We need to change it to update once a week; however, no matter what we do, we
can't remove or edit the existing backup schedule.
In the SQL Server Backup dialog box, regardless of whether the Destination
is removed and/or a new one is created, or if the Schedule is changed, none
of these new settings are ever saved. Why is this? What am I missing to get
around this?
Thanks,
Troy
Check your SQL Server agent jobs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a day.
> We need to change it to update once a week; however, no matter what we do, we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed, none
> of these new settings are ever saved. Why is this? What am I missing to get
> around this?
> Thanks,
> Troy
|||Hello,
Do you have enough previlages to update the job. Try login as SA and update
the job schedule using enterprise manager...
Thanks
Hari
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a
> day.
> We need to change it to update once a week; however, no matter what we do,
> we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed,
> none
> of these new settings are ever saved. Why is this? What am I missing to
> get
> around this?
> Thanks,
> Troy
|||Hello:
I am logged in under the SA account and trying to update the job in
enterprise manager. Is there something else I should be looking at or
resetting?
Thanks,
STroy
"Hari Prasad" wrote:

> Hello,
> Do you have enough previlages to update the job. Try login as SA and update
> the job schedule using enterprise manager...
> Thanks
> Hari
> "STroy" <STroy@.discussions.microsoft.com> wrote in message
> news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
>
>

Backing up SQL Databases

Hello:
How do you change the scheduled database backups in SQL Server 2000?
We have a scheduled backup of a production database that is run once a day.
We need to change it to update once a week; however, no matter what we do, we
can't remove or edit the existing backup schedule.
In the SQL Server Backup dialog box, regardless of whether the Destination
is removed and/or a new one is created, or if the Schedule is changed, none
of these new settings are ever saved. Why is this? What am I missing to get
around this?
Thanks,
TroyCheck your SQL Server agent jobs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a day.
> We need to change it to update once a week; however, no matter what we do, we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed, none
> of these new settings are ever saved. Why is this? What am I missing to get
> around this?
> Thanks,
> Troy|||Hello,
Do you have enough previlages to update the job. Try login as SA and update
the job schedule using enterprise manager...
Thanks
Hari
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a
> day.
> We need to change it to update once a week; however, no matter what we do,
> we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed,
> none
> of these new settings are ever saved. Why is this? What am I missing to
> get
> around this?
> Thanks,
> Troy|||Hello:
I am logged in under the SA account and trying to update the job in
enterprise manager. Is there something else I should be looking at or
resetting?
Thanks,
STroy
"Hari Prasad" wrote:
> Hello,
> Do you have enough previlages to update the job. Try login as SA and update
> the job schedule using enterprise manager...
> Thanks
> Hari
> "STroy" <STroy@.discussions.microsoft.com> wrote in message
> news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> > Hello:
> >
> > How do you change the scheduled database backups in SQL Server 2000?
> >
> > We have a scheduled backup of a production database that is run once a
> > day.
> > We need to change it to update once a week; however, no matter what we do,
> > we
> > can't remove or edit the existing backup schedule.
> >
> > In the SQL Server Backup dialog box, regardless of whether the Destination
> > is removed and/or a new one is created, or if the Schedule is changed,
> > none
> > of these new settings are ever saved. Why is this? What am I missing to
> > get
> > around this?
> >
> > Thanks,
> > Troy
>
>

Backing up SQL Databases

Hello:
How do you change the scheduled database backups in SQL Server 2000?
We have a scheduled backup of a production database that is run once a day.
We need to change it to update once a week; however, no matter what we do, w
e
can't remove or edit the existing backup schedule.
In the SQL Server Backup dialog box, regardless of whether the Destination
is removed and/or a new one is created, or if the Schedule is changed, none
of these new settings are ever saved. Why is this? What am I missing to get
around this?
Thanks,
TroyCheck your SQL Server agent jobs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a day
.
> We need to change it to update once a week; however, no matter what we do,
we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed, non
e
> of these new settings are ever saved. Why is this? What am I missing to ge
t
> around this?
> Thanks,
> Troy|||Hello,
Do you have enough previlages to update the job. Try login as SA and update
the job schedule using enterprise manager...
Thanks
Hari
"STroy" <STroy@.discussions.microsoft.com> wrote in message
news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
> Hello:
> How do you change the scheduled database backups in SQL Server 2000?
> We have a scheduled backup of a production database that is run once a
> day.
> We need to change it to update once a week; however, no matter what we do,
> we
> can't remove or edit the existing backup schedule.
> In the SQL Server Backup dialog box, regardless of whether the Destination
> is removed and/or a new one is created, or if the Schedule is changed,
> none
> of these new settings are ever saved. Why is this? What am I missing to
> get
> around this?
> Thanks,
> Troy|||Hello:
I am logged in under the SA account and trying to update the job in
enterprise manager. Is there something else I should be looking at or
resetting?
Thanks,
STroy
"Hari Prasad" wrote:

> Hello,
> Do you have enough previlages to update the job. Try login as SA and updat
e
> the job schedule using enterprise manager...
> Thanks
> Hari
> "STroy" <STroy@.discussions.microsoft.com> wrote in message
> news:4AADB0A7-E440-470F-BF1E-2B5134AB1899@.microsoft.com...
>
>

Backing up secondary DB in log shipping ...

Hello can someone clear this up for me?
In BOL "Log Shipping Tips and Best Practices" is the following
recommendation:
"Generating Database Backups from the Secondary
Since the log shipped database is only a small increment of time out
of sync with the primary database, it is a good idea to use it to
generate the full database backups. This would keep the primary
production server free of the potential overhead and contention
incurred by a daily (or scheduled) backup. "
In my experience and from searching other threads in this group this
is actually not true - backing up the log shipped database will not
work, it will fail with the error:
"Database is in warm-standby state (set by executing RESTORE WITH
STANDBY) and cannot be backed up until the entire load sequence is
completed."
Am I missing something or is BOL just being misleading?
thanks,
Peter
Peter,
http://support.microsoft.com/kb/311115 contains the correction.
Note: With SQL Server 2005, you it might be possible to create a snapshot
database over the secondary and back that up. (But I have no experience
with trying.)
RLF
<peter.wismer@.gmail.com> wrote in message
news:1187280994.613717.77730@.l22g2000prc.googlegro ups.com...
> Hello can someone clear this up for me?
> In BOL "Log Shipping Tips and Best Practices" is the following
> recommendation:
> "Generating Database Backups from the Secondary
> Since the log shipped database is only a small increment of time out
> of sync with the primary database, it is a good idea to use it to
> generate the full database backups. This would keep the primary
> production server free of the potential overhead and contention
> incurred by a daily (or scheduled) backup. "
> In my experience and from searching other threads in this group this
> is actually not true - backing up the log shipped database will not
> work, it will fail with the error:
> "Database is in warm-standby state (set by executing RESTORE WITH
> STANDBY) and cannot be backed up until the entire load sequence is
> completed."
> Am I missing something or is BOL just being misleading?
> thanks,
> Peter
>
|||On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Peter,
> http://support.microsoft.com/kb/311115contains the correction.
> Note: With SQL Server 2005, you it might be possible to create a snapshot
> database over the secondary and back that up. (But I have no experience
> with trying.)
> RLF<peter.wis...@.gmail.com> wrote in message
> news:1187280994.613717.77730@.l22g2000prc.googlegro ups.com...
>
>
>
>
>
> - Show quoted text -
Thanks very much Russell (I was beginning to mistrust my command of
the english language - thought I might need to find a Canadian
translation of BOL...)
Peter
|||I think it was a case of wishes versus reality. - RLF
<peter.wismer@.gmail.com> wrote in message
news:1187288061.528821.290710@.j4g2000prf.googlegro ups.com...
> On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Thanks very much Russell (I was beginning to mistrust my command of
> the english language - thought I might need to find a Canadian
> translation of BOL...)
> Peter
>

Backing up secondary DB in log shipping ...

Hello can someone clear this up for me?
In BOL "Log Shipping Tips and Best Practices" is the following
recommendation:
"Generating Database Backups from the Secondary
Since the log shipped database is only a small increment of time out
of sync with the primary database, it is a good idea to use it to
generate the full database backups. This would keep the primary
production server free of the potential overhead and contention
incurred by a daily (or scheduled) backup. "
In my experience and from searching other threads in this group this
is actually not true - backing up the log shipped database will not
work, it will fail with the error:
"Database is in warm-standby state (set by executing RESTORE WITH
STANDBY) and cannot be backed up until the entire load sequence is
completed."
Am I missing something or is BOL just being misleading?
thanks,
PeterPeter,
http://support.microsoft.com/kb/311115 contains the correction.
Note: With SQL Server 2005, you it might be possible to create a snapshot
database over the secondary and back that up. (But I have no experience
with trying.)
RLF
<peter.wismer@.gmail.com> wrote in message
news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
> Hello can someone clear this up for me?
> In BOL "Log Shipping Tips and Best Practices" is the following
> recommendation:
> "Generating Database Backups from the Secondary
> Since the log shipped database is only a small increment of time out
> of sync with the primary database, it is a good idea to use it to
> generate the full database backups. This would keep the primary
> production server free of the potential overhead and contention
> incurred by a daily (or scheduled) backup. "
> In my experience and from searching other threads in this group this
> is actually not true - backing up the log shipped database will not
> work, it will fail with the error:
> "Database is in warm-standby state (set by executing RESTORE WITH
> STANDBY) and cannot be backed up until the entire load sequence is
> completed."
> Am I missing something or is BOL just being misleading?
> thanks,
> Peter
>|||On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Peter,
> http://support.microsoft.com/kb/311115contains the correction.
> Note: With SQL Server 2005, you it might be possible to create a snapshot
> database over the secondary and back that up. (But I have no experience
> with trying.)
> RLF<peter.wis...@.gmail.com> wrote in message
> news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
>
> > Hello can someone clear this up for me?
> > In BOL "Log Shipping Tips and Best Practices" is the following
> > recommendation:
> > "Generating Database Backups from the Secondary
> > Since the log shipped database is only a small increment of time out
> > of sync with the primary database, it is a good idea to use it to
> > generate the full database backups. This would keep the primary
> > production server free of the potential overhead and contention
> > incurred by a daily (or scheduled) backup. "
> > In my experience and from searching other threads in this group this
> > is actually not true - backing up the log shipped database will not
> > work, it will fail with the error:
> > "Database is in warm-standby state (set by executing RESTORE WITH
> > STANDBY) and cannot be backed up until the entire load sequence is
> > completed."
> > Am I missing something or is BOL just being misleading?
> > thanks,
> > Peter- Hide quoted text -
> - Show quoted text -
Thanks very much Russell (I was beginning to mistrust my command of
the english language - thought I might need to find a Canadian
translation of BOL...)
Peter|||I think it was a case of wishes versus reality. - RLF
<peter.wismer@.gmail.com> wrote in message
news:1187288061.528821.290710@.j4g2000prf.googlegroups.com...
> On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Peter,
>> http://support.microsoft.com/kb/311115contains the correction.
>> Note: With SQL Server 2005, you it might be possible to create a snapshot
>> database over the secondary and back that up. (But I have no experience
>> with trying.)
>> RLF<peter.wis...@.gmail.com> wrote in message
>> news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
>>
>> > Hello can someone clear this up for me?
>> > In BOL "Log Shipping Tips and Best Practices" is the following
>> > recommendation:
>> > "Generating Database Backups from the Secondary
>> > Since the log shipped database is only a small increment of time out
>> > of sync with the primary database, it is a good idea to use it to
>> > generate the full database backups. This would keep the primary
>> > production server free of the potential overhead and contention
>> > incurred by a daily (or scheduled) backup. "
>> > In my experience and from searching other threads in this group this
>> > is actually not true - backing up the log shipped database will not
>> > work, it will fail with the error:
>> > "Database is in warm-standby state (set by executing RESTORE WITH
>> > STANDBY) and cannot be backed up until the entire load sequence is
>> > completed."
>> > Am I missing something or is BOL just being misleading?
>> > thanks,
>> > Peter- Hide quoted text -
>> - Show quoted text -
> Thanks very much Russell (I was beginning to mistrust my command of
> the english language - thought I might need to find a Canadian
> translation of BOL...)
> Peter
>

Backing up secondary DB in log shipping ...

Hello can someone clear this up for me?
In BOL "Log Shipping Tips and Best Practices" is the following
recommendation:
"Generating Database Backups from the Secondary
Since the log shipped database is only a small increment of time out
of sync with the primary database, it is a good idea to use it to
generate the full database backups. This would keep the primary
production server free of the potential overhead and contention
incurred by a daily (or scheduled) backup. "
In my experience and from searching other threads in this group this
is actually not true - backing up the log shipped database will not
work, it will fail with the error:
"Database is in warm-standby state (set by executing RESTORE WITH
STANDBY) and cannot be backed up until the entire load sequence is
completed."
Am I missing something or is BOL just being misleading?
thanks,
PeterPeter,
http://support.microsoft.com/kb/311115 contains the correction.
Note: With SQL Server 2005, you it might be possible to create a snapshot
database over the secondary and back that up. (But I have no experience
with trying.)
RLF
<peter.wismer@.gmail.com> wrote in message
news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
> Hello can someone clear this up for me?
> In BOL "Log Shipping Tips and Best Practices" is the following
> recommendation:
> "Generating Database Backups from the Secondary
> Since the log shipped database is only a small increment of time out
> of sync with the primary database, it is a good idea to use it to
> generate the full database backups. This would keep the primary
> production server free of the potential overhead and contention
> incurred by a daily (or scheduled) backup. "
> In my experience and from searching other threads in this group this
> is actually not true - backing up the log shipped database will not
> work, it will fail with the error:
> "Database is in warm-standby state (set by executing RESTORE WITH
> STANDBY) and cannot be backed up until the entire load sequence is
> completed."
> Am I missing something or is BOL just being misleading?
> thanks,
> Peter
>|||On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Peter,
> http://support.microsoft.com/kb/311115contains the correction.
> Note: With SQL Server 2005, you it might be possible to create a snapshot
> database over the secondary and back that up. (But I have no experience
> with trying.)
> RLF<peter.wis...@.gmail.com> wrote in message
> news:1187280994.613717.77730@.l22g2000prc.googlegroups.com...
>
>
>
>
>
>
>
>
> - Show quoted text -
Thanks very much Russell (I was beginning to mistrust my command of
the english language - thought I might need to find a Canadian
translation of BOL...)
Peter|||I think it was a case of wishes versus reality. - RLF
<peter.wismer@.gmail.com> wrote in message
news:1187288061.528821.290710@.j4g2000prf.googlegroups.com...
> On Aug 16, 1:12 pm, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Thanks very much Russell (I was beginning to mistrust my command of
> the english language - thought I might need to find a Canadian
> translation of BOL...)
> Peter
>

Backing up my DB on host

Hi,
I can make backup from my database but the SQL Server is on a
host(internet). The backup sets are placed on the host.
How can I create backups the way that backup sets relocate to my local PC.
Any help would be greatly appreciated.
Amin
I doubt that you will be able to do this. In order for it to happen your
SQL Server machine would have to be able to see the hard drives on your
machine. This talks about the database maintenance wizard, but the rules
apply to normal T-SQL backups as well:
http://support.microsoft.com/default...b;en-us;555128
What is your objective? Do you want to get your production data which is
located on the internet onto your machine? How far away from your host are
you? One option (although not a fun one) is driving to your host and
grabbing a tape/CD/DVD containing your backup file. Another option would be
to create a linked server from your PC (or local server) to your remote SQL
Server. You could then perform an INSERT INTO...SELECT (from the linked
server). One final option: Use a tool or script that creates insert
statements for you. you could then issue these statements on your local
machine.
Keith
"Amin Sobati" <amins@.morva.net> wrote in message
news:%23bu4uUxmEHA.2616@.tk2msftngp13.phx.gbl...
> Hi,
> I can make backup from my database but the SQL Server is on a
> host(internet). The backup sets are placed on the host.
> How can I create backups the way that backup sets relocate to my local PC.
> Any help would be greatly appreciated.
> Amin
>
|||Actually, you should be able to do it if they let you run backups. You need
to temporarily open up your computer to the internet and allow guest write
access to a file share on the computer. You can then get the IP address of
your computer and use the following command:
BACKUP DATABASE databasename
TO DISK = '\\10.1.0.1\share$\directory\file.bak'
Does your IP actually let you run backups though? That's kind of scary.
"Keith Kratochvil" wrote:

> I doubt that you will be able to do this. In order for it to happen your
> SQL Server machine would have to be able to see the hard drives on your
> machine. This talks about the database maintenance wizard, but the rules
> apply to normal T-SQL backups as well:
> http://support.microsoft.com/default...b;en-us;555128
> What is your objective? Do you want to get your production data which is
> located on the internet onto your machine? How far away from your host are
> you? One option (although not a fun one) is driving to your host and
> grabbing a tape/CD/DVD containing your backup file. Another option would be
> to create a linked server from your PC (or local server) to your remote SQL
> Server. You could then perform an INSERT INTO...SELECT (from the linked
> server). One final option: Use a tool or script that creates insert
> statements for you. you could then issue these statements on your local
> machine.
> --
> Keith
>
> "Amin Sobati" <amins@.morva.net> wrote in message
> news:%23bu4uUxmEHA.2616@.tk2msftngp13.phx.gbl...
>
|||I can't imagine that the network admins would want to turn off the firewall
or expose a machine on the internet.
If the [client] machine is available (visible) on the internet, then the
T-SQL BACKUP command backing up to the UNC should work (as long as the
account running SQL Server on the remote machine has rights to the share on
your computer). This is described within the KB article.
Keith
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:45E7E013-C3E6-49BC-98BE-43BC153AD276@.microsoft.com...
> Actually, you should be able to do it if they let you run backups. You
need
> to temporarily open up your computer to the internet and allow guest write
> access to a file share on the computer. You can then get the IP address
of[vbcol=seagreen]
> your computer and use the following command:
> BACKUP DATABASE databasename
> TO DISK = '\\10.1.0.1\share$\directory\file.bak'
> Does your IP actually let you run backups though? That's kind of scary.
> "Keith Kratochvil" wrote:
your[vbcol=seagreen]
rules[vbcol=seagreen]
is[vbcol=seagreen]
are[vbcol=seagreen]
would be[vbcol=seagreen]
SQL[vbcol=seagreen]
linked[vbcol=seagreen]
PC.[vbcol=seagreen]
sql

Backing up my DB on host

Hi,
I can make backup from my database but the SQL Server is on a
host(internet). The backup sets are placed on the host.
How can I create backups the way that backup sets relocate to my local PC.
Any help would be greatly appreciated.
AminI doubt that you will be able to do this. In order for it to happen your
SQL Server machine would have to be able to see the hard drives on your
machine. This talks about the database maintenance wizard, but the rules
apply to normal T-SQL backups as well:
http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
What is your objective? Do you want to get your production data which is
located on the internet onto your machine? How far away from your host are
you? One option (although not a fun one) is driving to your host and
grabbing a tape/CD/DVD containing your backup file. Another option would be
to create a linked server from your PC (or local server) to your remote SQL
Server. You could then perform an INSERT INTO...SELECT (from the linked
server). One final option: Use a tool or script that creates insert
statements for you. you could then issue these statements on your local
machine.
--
Keith
"Amin Sobati" <amins@.morva.net> wrote in message
news:%23bu4uUxmEHA.2616@.tk2msftngp13.phx.gbl...
> Hi,
> I can make backup from my database but the SQL Server is on a
> host(internet). The backup sets are placed on the host.
> How can I create backups the way that backup sets relocate to my local PC.
> Any help would be greatly appreciated.
> Amin
>|||I can't imagine that the network admins would want to turn off the firewall
or expose a machine on the internet.
If the [client] machine is available (visible) on the internet, then the
T-SQL BACKUP command backing up to the UNC should work (as long as the
account running SQL Server on the remote machine has rights to the share on
your computer). This is described within the KB article.
--
Keith
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:45E7E013-C3E6-49BC-98BE-43BC153AD276@.microsoft.com...
> Actually, you should be able to do it if they let you run backups. You
need
> to temporarily open up your computer to the internet and allow guest write
> access to a file share on the computer. You can then get the IP address
of
> your computer and use the following command:
> BACKUP DATABASE databasename
> TO DISK = '\\10.1.0.1\share$\directory\file.bak'
> Does your IP actually let you run backups though? That's kind of scary.
> "Keith Kratochvil" wrote:
> > I doubt that you will be able to do this. In order for it to happen
your
> > SQL Server machine would have to be able to see the hard drives on your
> > machine. This talks about the database maintenance wizard, but the
rules
> > apply to normal T-SQL backups as well:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >
> > What is your objective? Do you want to get your production data which
is
> > located on the internet onto your machine? How far away from your host
are
> > you? One option (although not a fun one) is driving to your host and
> > grabbing a tape/CD/DVD containing your backup file. Another option
would be
> > to create a linked server from your PC (or local server) to your remote
SQL
> > Server. You could then perform an INSERT INTO...SELECT (from the
linked
> > server). One final option: Use a tool or script that creates insert
> > statements for you. you could then issue these statements on your local
> > machine.
> >
> > --
> > Keith
> >
> >
> > "Amin Sobati" <amins@.morva.net> wrote in message
> > news:%23bu4uUxmEHA.2616@.tk2msftngp13.phx.gbl...
> > > Hi,
> > > I can make backup from my database but the SQL Server is on a
> > > host(internet). The backup sets are placed on the host.
> > > How can I create backups the way that backup sets relocate to my local
PC.
> > > Any help would be greatly appreciated.
> > > Amin
> > >
> > >
> >
> >

Backing up databases in a mirror configuration

I have a user database maintance plan with subplans for full and
transaction log backups deployed to both the Principal and Mirror
servers. Each subplan has its own schedule.
Obviously, the principal server executes a successfully backup, while
the mirror copy fails. This generates errors that are picked up by
MOM and also from the jobs themselves.
In order to eliminate these errors, I emplyed a method that prevents
the jobs from running if the server is hosting the mirror copy (note
that all the databases on the server are mirrored):
1) Remove the schedule from the job that runs the SSIS package - job
name 'User Databases.Full Database Backup'
2) Create a new job called 'User Databases.Full Database Backup Status
Check' that checks for the read/write and online status of the
databases and executes the job in step one if they are online
3) Add a schedule to the job 'User Databases.Full Database Backup
Status Check' with the same details as that removed in step 1
I have a big problem with this approach: if any of the databases are
the mirror, then the entire backup subplan is not run - even if some
of the databases are the principal on the same server - it's an all or
nothing approach since the databases checked in step 2 may not
necessarily match the list of databases defined in the subplan.
Clearly, I'd like the checking step to only be affected by the
databases defined in the subplan, but I cannot think of a way of
interrogating the subplan details using SQL code to determine this.
Ideally, I would like to edit the maintenance plan's list of databases
to only include databases that are the principal on that server and to
do it each time the job is executed - maybe using the two job approach
as described above.
I would like some advice on a way to do this or whether I am barking
up the wrong tree and should try a different angle - perhaps defining
my own backup process (I really want to avoid doing this). Clearly,
if the maintenance plan could detect the fact that the database is a
mirror copy and just skip it, the whole use goes away, but it does
not.
Thanks> I would like some advice on a way to do this or whether I am barking
> up the wrong tree and should try a different angle - perhaps defining
> my own backup process (I really want to avoid doing this).
This is what you would have to do. Maint plans are for simpler installations
, and conditionally
handling a mirrored database *inside* a backup task is not available. Consid
er wishing this at
connect.microsoft.com.
Another options is to have one backup task per database, and have a TSQL tas
k before each which
check the mirroring catalog views and if a mirror, moves to the next databas
e instead. A bit messy,
but should be doable.
Having your own scripts for performing a backup isn't difficult, though. You
can still use the maint
plan to remove old backup files. (Google for how to generate the backup comm
and with a time stamp in
the file name and you will find examples...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Viracochas" <warmtea@.hotmail.com> wrote in message
news:1179742488.051578.275990@.b40g2000prd.googlegroups.com...
>I have a user database maintance plan with subplans for full and
> transaction log backups deployed to both the Principal and Mirror
> servers. Each subplan has its own schedule.
> Obviously, the principal server executes a successfully backup, while
> the mirror copy fails. This generates errors that are picked up by
> MOM and also from the jobs themselves.
> In order to eliminate these errors, I emplyed a method that prevents
> the jobs from running if the server is hosting the mirror copy (note
> that all the databases on the server are mirrored):
> 1) Remove the schedule from the job that runs the SSIS package - job
> name 'User Databases.Full Database Backup'
> 2) Create a new job called 'User Databases.Full Database Backup Status
> Check' that checks for the read/write and online status of the
> databases and executes the job in step one if they are online
> 3) Add a schedule to the job 'User Databases.Full Database Backup
> Status Check' with the same details as that removed in step 1
> I have a big problem with this approach: if any of the databases are
> the mirror, then the entire backup subplan is not run - even if some
> of the databases are the principal on the same server - it's an all or
> nothing approach since the databases checked in step 2 may not
> necessarily match the list of databases defined in the subplan.
> Clearly, I'd like the checking step to only be affected by the
> databases defined in the subplan, but I cannot think of a way of
> interrogating the subplan details using SQL code to determine this.
> Ideally, I would like to edit the maintenance plan's list of databases
> to only include databases that are the principal on that server and to
> do it each time the job is executed - maybe using the two job approach
> as described above.
> I would like some advice on a way to do this or whether I am barking
> up the wrong tree and should try a different angle - perhaps defining
> my own backup process (I really want to avoid doing this). Clearly,
> if the maintenance plan could detect the fact that the database is a
> mirror copy and just skip it, the whole use goes away, but it does
> not.
> Thanks
>|||On 21 May, 13:43, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> This is what you would have to do. Maint plans are for simpler installatio
ns, and conditionally
> handling a mirrored database *inside* a backup task is not available. Cons
ider wishing this at
> connect.microsoft.com.
> Another options is to have one backup task per database, and have a TSQL t
ask before each which
> check the mirroring catalog views and if a mirror, moves to the next datab
ase instead. A bit messy,
> but should be doable.
> Having your own scripts for performing a backup isn't difficult, though. Y
ou can still use the maint
> plan to remove old backup files. (Google for how to generate the backup co
mmand with a time stamp in
> the file name and you will find examples...)
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> "Viracochas" <warm...@.hotmail.com> wrote in message
> news:1179742488.051578.275990@.b40g2000prd.googlegroups.com...
Thanks for the feedback. I feared there was no easy way, though it
won't be too difficult to set it up.

Backing up databases in a mirror configuration

I have a user database maintance plan with subplans for full and
transaction log backups deployed to both the Principal and Mirror
servers. Each subplan has its own schedule.
Obviously, the principal server executes a successfully backup, while
the mirror copy fails. This generates errors that are picked up by
MOM and also from the jobs themselves.
In order to eliminate these errors, I emplyed a method that prevents
the jobs from running if the server is hosting the mirror copy (note
that all the databases on the server are mirrored):
1) Remove the schedule from the job that runs the SSIS package - job
name 'User Databases.Full Database Backup'
2) Create a new job called 'User Databases.Full Database Backup Status
Check' that checks for the read/write and online status of the
databases and executes the job in step one if they are online
3) Add a schedule to the job 'User Databases.Full Database Backup
Status Check' with the same details as that removed in step 1
I have a big problem with this approach: if any of the databases are
the mirror, then the entire backup subplan is not run - even if some
of the databases are the principal on the same server - it's an all or
nothing approach since the databases checked in step 2 may not
necessarily match the list of databases defined in the subplan.
Clearly, I'd like the checking step to only be affected by the
databases defined in the subplan, but I cannot think of a way of
interrogating the subplan details using SQL code to determine this.
Ideally, I would like to edit the maintenance plan's list of databases
to only include databases that are the principal on that server and to
do it each time the job is executed - maybe using the two job approach
as described above.
I would like some advice on a way to do this or whether I am barking
up the wrong tree and should try a different angle - perhaps defining
my own backup process (I really want to avoid doing this). Clearly,
if the maintenance plan could detect the fact that the database is a
mirror copy and just skip it, the whole use goes away, but it does
not.
Thanks> I would like some advice on a way to do this or whether I am barking
> up the wrong tree and should try a different angle - perhaps defining
> my own backup process (I really want to avoid doing this).
This is what you would have to do. Maint plans are for simpler installations, and conditionally
handling a mirrored database *inside* a backup task is not available. Consider wishing this at
connect.microsoft.com.
Another options is to have one backup task per database, and have a TSQL task before each which
check the mirroring catalog views and if a mirror, moves to the next database instead. A bit messy,
but should be doable.
Having your own scripts for performing a backup isn't difficult, though. You can still use the maint
plan to remove old backup files. (Google for how to generate the backup command with a time stamp in
the file name and you will find examples...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Viracochas" <warmtea@.hotmail.com> wrote in message
news:1179742488.051578.275990@.b40g2000prd.googlegroups.com...
>I have a user database maintance plan with subplans for full and
> transaction log backups deployed to both the Principal and Mirror
> servers. Each subplan has its own schedule.
> Obviously, the principal server executes a successfully backup, while
> the mirror copy fails. This generates errors that are picked up by
> MOM and also from the jobs themselves.
> In order to eliminate these errors, I emplyed a method that prevents
> the jobs from running if the server is hosting the mirror copy (note
> that all the databases on the server are mirrored):
> 1) Remove the schedule from the job that runs the SSIS package - job
> name 'User Databases.Full Database Backup'
> 2) Create a new job called 'User Databases.Full Database Backup Status
> Check' that checks for the read/write and online status of the
> databases and executes the job in step one if they are online
> 3) Add a schedule to the job 'User Databases.Full Database Backup
> Status Check' with the same details as that removed in step 1
> I have a big problem with this approach: if any of the databases are
> the mirror, then the entire backup subplan is not run - even if some
> of the databases are the principal on the same server - it's an all or
> nothing approach since the databases checked in step 2 may not
> necessarily match the list of databases defined in the subplan.
> Clearly, I'd like the checking step to only be affected by the
> databases defined in the subplan, but I cannot think of a way of
> interrogating the subplan details using SQL code to determine this.
> Ideally, I would like to edit the maintenance plan's list of databases
> to only include databases that are the principal on that server and to
> do it each time the job is executed - maybe using the two job approach
> as described above.
> I would like some advice on a way to do this or whether I am barking
> up the wrong tree and should try a different angle - perhaps defining
> my own backup process (I really want to avoid doing this). Clearly,
> if the maintenance plan could detect the fact that the database is a
> mirror copy and just skip it, the whole use goes away, but it does
> not.
> Thanks
>|||On 21 May, 13:43, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> > I would like some advice on a way to do this or whether I am barking
> > up the wrong tree and should try a different angle - perhaps defining
> > my own backup process (I really want to avoid doing this).
> This is what you would have to do. Maint plans are for simpler installations, and conditionally
> handling a mirrored database *inside* a backup task is not available. Consider wishing this at
> connect.microsoft.com.
> Another options is to have one backup task per database, and have a TSQL task before each which
> check the mirroring catalog views and if a mirror, moves to the next database instead. A bit messy,
> but should be doable.
> Having your own scripts for performing a backup isn't difficult, though. You can still use the maint
> plan to remove old backup files. (Google for how to generate the backup command with a time stamp in
> the file name and you will find examples...)
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Viracochas" <warm...@.hotmail.com> wrote in message
> news:1179742488.051578.275990@.b40g2000prd.googlegroups.com...
Thanks for the feedback. I feared there was no easy way, though it
won't be too difficult to set it up.

Backing Up Data

Hello
I have a MSSQL database supplied by my web host. I'd like to be able to perf
orm periodic backups (1 or more times a week). The database is small and I h
ave a fast connection so the speed isn't a problem. I would like the backups
to be automated. I have a
linux server where I'd like to store the data, I'm not sure if this can be d
one? How do users backup?
Thanks
DiDianne
Please refer to the BOL on BACKUP DATABASE databasename TO......
"Dianne" <anonymous@.discussions.microsoft.com> wrote in message
news:A12148F5-B98A-48AD-8B57-429976325C87@.microsoft.com...
> Hello
> I have a MSSQL database supplied by my web host. I'd like to be able to
perform periodic backups (1 or more times a week). The database is small and
I have a fast connection so the speed isn't a problem. I would like the
backups to be automated. I have a linux server where I'd like to store the
data, I'm not sure if this can be done? How do users backup?
> Thanks
> Di|||hi dianne,
you can automate backup process using Enterprise manager.
open enterprise manager,click on the any user database. go to the Tools menu
, click on
database maintenance planner. click next, check the required database you wa
nt. click next 2
times(since they are not specific to backup) you will come to a screen "spec
ify the database
backup plan". you can specify the destination as tape or disk. on the same s
creen you will get
an option to schedule(click the required frequency). click next, here you ca
n specify the
directory to which backup file will go. on the next screen if required sched
ule "tran. log"
backup.
This way you can automate the database backup using Enterprise manager.
<<
Never done above process, so you may have to take care of some OS level util
ity to transfer
backup files to linux server.
Vishal Parkar
vgparkar@.yahoo.co.in|||Hi,
1.Execute the BACKUP database command to backup the database to SQL server
local hard disk drive
2. Using FTP send the Backup file to Linux machine
How to automate
--
1. Using OSQL -Usa -Ppassword -Sserver -Q"backup database dbname to
disk='c:\backup\dbanme.bak' with init'
2. FTP the dbname.bak file to Linux server ip.
You can put the avobe 2 in a batch file and schedule it thru SQL agent ..
Jobs.
Thanks
Hari
MCDBA
"Dianne" <anonymous@.discussions.microsoft.com> wrote in message
news:A12148F5-B98A-48AD-8B57-429976325C87@.microsoft.com...
> Hello
> I have a MSSQL database supplied by my web host. I'd like to be able to
perform periodic backups (1 or more times a week). The database is small and
I have a fast connection so the speed isn't a problem. I would like the
backups to be automated. I have a linux server where I'd like to store the
data, I'm not sure if this can be done? How do users backup?
> Thanks
> Di|||Thank you very much. I appreciate all your help.
I may be missing something, and I am new to MSSQL. My access to the host run
ning MSSQL is limited. It's a web host account and I only have access using
Enterprise Manager on my workstation. I haven't got access to Windows server
s to run an agent at my end
and I can't on the host either because I don't have the permssions.
It looks like I will need a Windows server to do this?
Thank you.

Backing up and restoring 50 databases to a new server

I would like to replace my SQL 2000 server with a faster box. I currently
use a combination of full and transactional backups to back up the server
every day. I know that I could build a new box and restore each database
from backup file one at a time but was wondering if there was a quicker way
to store all the databases
Hi,
Look in to the below web sites for various strategies to move all the
databases to new server.
Moving SQL Server Databases to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=224071
Moving DB's between Servers
http://www.support.microsoft.com/?id=314546
Thanks
Hari
MCDBA
"Richard Zellmer" <tdmailbox@.yahoo.com> wrote in message
news:#$TGJe7IEHA.1412@.TK2MSFTNGP12.phx.gbl...
> I would like to replace my SQL 2000 server with a faster box. I currently
> use a combination of full and transactional backups to back up the server
> every day. I know that I could build a new box and restore each database
> from backup file one at a time but was wondering if there was a quicker
way
> to store all the databases
>
>
|||If you have installed SQL on the new server with the same paths... I have stopped the SQL services on both servers and copied all DB's including system to the new server. I have done this on many occasions. I always double check @.@.servername on the ne
w server when I am done.
On the new server just rename the SQL Directories before you copy the old ones over. This will give you something to fall back on just in case of failure. Copy all the mdf's and ldf's to the same location on the new box.
Jeff
MCDBA, MCSE+I

Backing up and restoring 50 databases to a new server

I would like to replace my SQL 2000 server with a faster box. I currently
use a combination of full and transactional backups to back up the server
every day. I know that I could build a new box and restore each database
from backup file one at a time but was wondering if there was a quicker way
to store all the databasesHi,
Look in to the below web sites for various strategies to move all the
databases to new server.
Moving SQL Server Databases to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=224071
Moving DB's between Servers
http://www.support.microsoft.com/?id=314546
Thanks
Hari
MCDBA
"Richard Zellmer" <tdmailbox@.yahoo.com> wrote in message
news:#$TGJe7IEHA.1412@.TK2MSFTNGP12.phx.gbl...
> I would like to replace my SQL 2000 server with a faster box. I currently
> use a combination of full and transactional backups to back up the server
> every day. I know that I could build a new box and restore each database
> from backup file one at a time but was wondering if there was a quicker
way
> to store all the databases
>
>

Backing up and restoring 50 databases to a new server

I would like to replace my SQL 2000 server with a faster box. I currently
use a combination of full and transactional backups to back up the server
every day. I know that I could build a new box and restore each database
from backup file one at a time but was wondering if there was a quicker way
to store all the databasesHi,
Look in to the below web sites for various strategies to move all the
databases to new server.
Moving SQL Server Databases to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=224071
Moving DB's between Servers
http://www.support.microsoft.com/?id=314546
Thanks
Hari
MCDBA
"Richard Zellmer" <tdmailbox@.yahoo.com> wrote in message
news:#$TGJe7IEHA.1412@.TK2MSFTNGP12.phx.gbl...
> I would like to replace my SQL 2000 server with a faster box. I currently
> use a combination of full and transactional backups to back up the server
> every day. I know that I could build a new box and restore each database
> from backup file one at a time but was wondering if there was a quicker
way
> to store all the databases
>
>|||If you have installed SQL on the new server with the same paths... I have
stopped the SQL services on both servers and copied all DB's including syste
m to the new server. I have done this on many occasions. I always double c
heck @.@.servername on the ne
w server when I am done.
On the new server just rename the SQL Directories before you copy the old on
es over. This will give you something to fall back on just in case of failu
re. Copy all the mdf's and ldf's to the same location on the new box.
Jeff
MCDBA, MCSE+I

Backing up an active database

I have an active database running on SQL Server 2000. I use the backup
software Backup Exec 9. When I do my backups, I backup all working
directories. When I do a test restore, I notice that the database does not
backup but all the other files in the directory does. What am I not doing
correctly? Any help is appreciated.
Do a SQL Backup. Backup Exec is trying to copy the sql files that are in use
by SQL Server so you won't be able to copy them.
Set up a maintenance plan to do sql backups and use backup exec to backup
the SQL backup files.
"Peter McCaul" <compcoff@.hotmail.com> wrote in message
news:e3ZNoJLHEHA.2472@.TK2MSFTNGP10.phx.gbl...
> I have an active database running on SQL Server 2000. I use the backup
> software Backup Exec 9. When I do my backups, I backup all working
> directories. When I do a test restore, I notice that the database does
not
> backup but all the other files in the directory does. What am I not doing
> correctly? Any help is appreciated.
>

Backing up an active database

I have an active database running on SQL Server 2000. I use the backup
software Backup Exec 9. When I do my backups, I backup all working
directories. When I do a test restore, I notice that the database does not
backup but all the other files in the directory does. What am I not doing
correctly? Any help is appreciated.Do a SQL Backup. Backup Exec is trying to copy the sql files that are in use
by SQL Server so you won't be able to copy them.
Set up a maintenance plan to do sql backups and use backup exec to backup
the SQL backup files.
"Peter McCaul" <compcoff@.hotmail.com> wrote in message
news:e3ZNoJLHEHA.2472@.TK2MSFTNGP10.phx.gbl...
> I have an active database running on SQL Server 2000. I use the backup
> software Backup Exec 9. When I do my backups, I backup all working
> directories. When I do a test restore, I notice that the database does
not
> backup but all the other files in the directory does. What am I not doing
> correctly? Any help is appreciated.
>|||Hi,
R U trying to backup .mdf and .ldf files online?. Very few
backup softwares support Open File backup. Look into the
log of backup tool if any errors are thrown. Also it is
not a good idea to take backups of open files. you can
generate backup of the databases using maintenance plans
or scripts then use the backup tool to move them into
DATs/LTO's.
If you still insist to backup the .mdf and ldf files,which
I would not prefer for larger databases, you can schedule
as
1.Detach Database(s)
2.Backup .mdf & .ldf files using the backup software.
3.Attach Database(s)& corresponding tran. logs.
Someone may also suggest to stop SQL Server and backup
the .mdf and .ldf files, but there are chances for
failures while attaching them.
HTH
Regards
Thirumal
>--Original Message--
>I have an active database running on SQL Server 2000. I
use the backup
>software Backup Exec 9. When I do my backups, I backup
all working
>directories. When I do a test restore, I notice that the
database does not
>backup but all the other files in the directory does.
What am I not doing
>correctly? Any help is appreciated.
>
>.
>

Backing up an active database

I have an active database running on SQL Server 2000. I use the backup
software Backup Exec 9. When I do my backups, I backup all working
directories. When I do a test restore, I notice that the database does not
backup but all the other files in the directory does. What am I not doing
correctly? Any help is appreciated.Do a SQL Backup. Backup Exec is trying to copy the sql files that are in use
by SQL Server so you won't be able to copy them.
Set up a maintenance plan to do sql backups and use backup exec to backup
the SQL backup files.
"Peter McCaul" <compcoff@.hotmail.com> wrote in message
news:e3ZNoJLHEHA.2472@.TK2MSFTNGP10.phx.gbl...
> I have an active database running on SQL Server 2000. I use the backup
> software Backup Exec 9. When I do my backups, I backup all working
> directories. When I do a test restore, I notice that the database does
not
> backup but all the other files in the directory does. What am I not doing
> correctly? Any help is appreciated.
>

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.
>