|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
Hollywood0728
Guest
|
 Posted: Thu Oct 25, 2007 9:56 am Post subject: SQL Backup |
 |
|
My knowledge of SQL is very little, I will start there. I can't seem to find
the answer in BOLD text that I am looking for so I will ask the public. Is
it a fact then when using the windows based backup tool that SQL server stops
running, the backup is made, then SQL starts it self again?? Or do I
manually have to stop it, and start it? I would think I don't want the SQL
database to stop running so I am assuming they have third party software that
will backup while the database is running? Can I use the SQL integrated
backup tool instead of the windows backup tool? Or does it do the same
thing? Thanks. |
|
| Back to top |
|
 |
|
|
TBone
Guest
|
| Posted: Thu Oct 25, 2007 1:49 pm Post subject: Re: SQL Backup |
|
|
And on the eigth day <stevenjwilliams83@yahoo.com> did cause the
electrons to come together and form the following words:
| Quote: | Is it a fact then when using the windows based backup
tool that SQL server stops running, the backup is made, then SQL
starts it self again??
|
Can't say I've actually tried it, because it probably wouldn't work
anyway. Most likely, backup would skip the actual database files becuase
they were in use.
| Quote: | Can I use the SQL integrated backup tool instead of the windows backup
tool? Or does it do the same thing? |
Can you? How about *you should always use the integrated backup tool*.
There... its in bold or at least as best as we can do with plain text.
-------
T-Bone
MCNGP XL |
|
| Back to top |
|
|
John R
Guest
|
| Posted: Thu Oct 25, 2007 6:17 pm Post subject: Re: SQL Backup |
|
|
"Hollywood0728" <stevenjwilliams83@yahoo.com> wrote in message
news:E735D0B1-66C5-4354-8DEF-610D47234F91@microsoft.com...
| Quote: | My knowledge of SQL is very little, I will start there. I can't seem to
find
the answer in BOLD text that I am looking for so I will ask the public.
Is
it a fact then when using the windows based backup tool that SQL server
stops
running, the backup is made, then SQL starts it self again?? Or do I
manually have to stop it, and start it? I would think I don't want the
SQL
database to stop running so I am assuming they have third party software
that
will backup while the database is running? Can I use the SQL integrated
backup tool instead of the windows backup tool? Or does it do the same
thing? Thanks.
|
You should use the integrated backup tool to create your DB backups, and
then use your Enterprise backup solution to backup the SQL backup files,
unless your Enterprise backup solution has an SQL plug-in.
We backup all of our SQL databases through the integrated tool at say 10pm
to a shared folder. Our Enterprise backup then backs up the share at 1am.
If we need to restore, we simply restore the backup share, and then use SQL
to pull the backup from there back into the DB. Maybe not the most
efficient way to do it, but certainly effective.
John R |
|
| Back to top |
|
|
Hollywood0728
Guest
|
| Posted: Thu Oct 25, 2007 6:21 pm Post subject: Re: SQL Backup |
|
|
Well I guess the sarcasm wasn't needed. Atleast I was upfront about my
little knowledge of SQL. But Thanks, I guess.
"TBone" wrote:
| Quote: | And on the eigth day <stevenjwilliams83@yahoo.com> did cause the
electrons to come together and form the following words:
Is it a fact then when using the windows based backup
tool that SQL server stops running, the backup is made, then SQL
starts it self again??
Can't say I've actually tried it, because it probably wouldn't work
anyway. Most likely, backup would skip the actual database files becuase
they were in use.
Can I use the SQL integrated backup tool instead of the windows backup
tool? Or does it do the same thing?
Can you? How about *you should always use the integrated backup tool*.
There... its in bold or at least as best as we can do with plain text.
-------
T-Bone
MCNGP XL
|
|
|
| Back to top |
|
|
kpg*
Guest
|
| Posted: Thu Oct 25, 2007 6:32 pm Post subject: Re: SQL Backup |
|
|
=?Utf-8?B?SG9sbHl3b29kMDcyOA==?= <stevenjwilliams83@yahoo.com> wrote in
news:F254EF95-768B-42B4-8C11-8DDC9D4DB78A@microsoft.com:
| Quote: | Well I guess the sarcasm wasn't needed. Atleast I was upfront about
my little knowledge of SQL. But Thanks, I guess.
|
A simple Thank you would have sufficed. Where your manners? |
|
| Back to top |
|
|
Hollywood0728
Guest
|
| Posted: Fri Oct 26, 2007 12:58 am Post subject: Re: SQL Backup |
|
|
John -
I currently have 1 SQL server 2000 in the mix. I am having troubles getting
the back up to work over the network? Have you ran into any trouble like
this? Is there a script that needs to be written to achieve this? Thanks in
advance.
"John R" wrote:
| Quote: |
"Hollywood0728" <stevenjwilliams83@yahoo.com> wrote in message
news:E735D0B1-66C5-4354-8DEF-610D47234F91@microsoft.com...
My knowledge of SQL is very little, I will start there. I can't seem to
find
the answer in BOLD text that I am looking for so I will ask the public.
Is
it a fact then when using the windows based backup tool that SQL server
stops
running, the backup is made, then SQL starts it self again?? Or do I
manually have to stop it, and start it? I would think I don't want the
SQL
database to stop running so I am assuming they have third party software
that
will backup while the database is running? Can I use the SQL integrated
backup tool instead of the windows backup tool? Or does it do the same
thing? Thanks.
You should use the integrated backup tool to create your DB backups, and
then use your Enterprise backup solution to backup the SQL backup files,
unless your Enterprise backup solution has an SQL plug-in.
We backup all of our SQL databases through the integrated tool at say 10pm
to a shared folder. Our Enterprise backup then backs up the share at 1am.
If we need to restore, we simply restore the backup share, and then use SQL
to pull the backup from there back into the DB. Maybe not the most
efficient way to do it, but certainly effective.
John R
|
|
|
| Back to top |
|
|
John R
Guest
|
| Posted: Fri Oct 26, 2007 12:58 am Post subject: Re: SQL Backup |
|
|
We use Enterprise manager SQL Server Agent Job to backup each database to a
folder on the SQL box locally. That folder is shared on the network. Then,
Veritas comes along each night at a later time to backup the shared folder.
But to answer your question, we create the backups on the local server, and
then the backup server comes along and copies it over the network.
John R
"Hollywood0728" <stevenjwilliams83@yahoo.com> wrote in message
news:676F3319-7D46-4C7F-92E1-144D586A7EC4@microsoft.com...
| Quote: | John -
I currently have 1 SQL server 2000 in the mix. I am having troubles
getting
the back up to work over the network? Have you ran into any trouble like
this? Is there a script that needs to be written to achieve this? Thanks
in
advance.
"John R" wrote:
"Hollywood0728" <stevenjwilliams83@yahoo.com> wrote in message
news:E735D0B1-66C5-4354-8DEF-610D47234F91@microsoft.com...
My knowledge of SQL is very little, I will start there. I can't seem
to
find
the answer in BOLD text that I am looking for so I will ask the public.
Is
it a fact then when using the windows based backup tool that SQL server
stops
running, the backup is made, then SQL starts it self again?? Or do I
manually have to stop it, and start it? I would think I don't want the
SQL
database to stop running so I am assuming they have third party
software
that
will backup while the database is running? Can I use the SQL
integrated
backup tool instead of the windows backup tool? Or does it do the same
thing? Thanks.
You should use the integrated backup tool to create your DB backups, and
then use your Enterprise backup solution to backup the SQL backup files,
unless your Enterprise backup solution has an SQL plug-in.
We backup all of our SQL databases through the integrated tool at say
10pm
to a shared folder. Our Enterprise backup then backs up the share at
1am.
If we need to restore, we simply restore the backup share, and then use
SQL
to pull the backup from there back into the DB. Maybe not the most
efficient way to do it, but certainly effective.
John R
|
|
|
| Back to top |
|
|
|
|
|
|
