I currently have a main database server and want to implement a backup
server that replicates the data in my main server.
What is the best method of implementing this? I really don't know where to
start so even a pointer at some reading material would be helpful. Any
advice will be appreciated.
Hi
Look up Log Shipping and Replication in BOL (or the Microsoft web site).
Those are your 2 built-in options.
Regards
Mike
"Michael" wrote:
> I currently have a main database server and want to implement a backup
> server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
>
|||That depends on if you want to copy all of the data or a subset of the data.
If you want all the data and system objects and your destination database
can go offline while the transaction logs are applied, and is read only,
then log shipping is for you.
If you want only a subset of the data and don't care about the system
objects (like permissions, etc), need continualy accessability of the
destination database, and want to be able to update the destination database
use replication. Note that if you are not careful the updates you make on
the destination database can disrupt the replication process, but you can
partition your data so it doesn't.
"Michael" <michael@.hello.com> wrote in message
news:356vljF4i904nU1@.individual.net...
>I currently have a main database server and want to implement a backup
>server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
Showing posts with label implement. Show all posts
Showing posts with label implement. Show all posts
Thursday, March 22, 2012
Backup server
I currently have a main database server and want to implement a backup
server that replicates the data in my main server.
What is the best method of implementing this? I really don't know where to
start so even a pointer at some reading material would be helpful. Any
advice will be appreciated.
Hi
Look up Log Shipping and Replication in BOL (or the Microsoft web site).
Those are your 2 built-in options.
Regards
Mike
"Michael" wrote:
> I currently have a main database server and want to implement a backup
> server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
>
|||That depends on if you want to copy all of the data or a subset of the data.
If you want all the data and system objects and your destination database
can go offline while the transaction logs are applied, and is read only,
then log shipping is for you.
If you want only a subset of the data and don't care about the system
objects (like permissions, etc), need continualy accessability of the
destination database, and want to be able to update the destination database
use replication. Note that if you are not careful the updates you make on
the destination database can disrupt the replication process, but you can
partition your data so it doesn't.
"Michael" <michael@.hello.com> wrote in message
news:356vljF4i904nU1@.individual.net...
>I currently have a main database server and want to implement a backup
>server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
sql
server that replicates the data in my main server.
What is the best method of implementing this? I really don't know where to
start so even a pointer at some reading material would be helpful. Any
advice will be appreciated.
Hi
Look up Log Shipping and Replication in BOL (or the Microsoft web site).
Those are your 2 built-in options.
Regards
Mike
"Michael" wrote:
> I currently have a main database server and want to implement a backup
> server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
>
|||That depends on if you want to copy all of the data or a subset of the data.
If you want all the data and system objects and your destination database
can go offline while the transaction logs are applied, and is read only,
then log shipping is for you.
If you want only a subset of the data and don't care about the system
objects (like permissions, etc), need continualy accessability of the
destination database, and want to be able to update the destination database
use replication. Note that if you are not careful the updates you make on
the destination database can disrupt the replication process, but you can
partition your data so it doesn't.
"Michael" <michael@.hello.com> wrote in message
news:356vljF4i904nU1@.individual.net...
>I currently have a main database server and want to implement a backup
>server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
sql
Backup server
I currently have a main database server and want to implement a backup
server that replicates the data in my main server.
What is the best method of implementing this? I really don't know where to
start so even a pointer at some reading material would be helpful. Any
advice will be appreciated.Hi
Look up Log Shipping and Replication in BOL (or the Microsoft web site).
Those are your 2 built-in options.
Regards
Mike
"Michael" wrote:
> I currently have a main database server and want to implement a backup
> server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
>|||That depends on if you want to copy all of the data or a subset of the data.
If you want all the data and system objects and your destination database
can go offline while the transaction logs are applied, and is read only,
then log shipping is for you.
If you want only a subset of the data and don't care about the system
objects (like permissions, etc), need continualy accessability of the
destination database, and want to be able to update the destination database
use replication. Note that if you are not careful the updates you make on
the destination database can disrupt the replication process, but you can
partition your data so it doesn't.
"Michael" <michael@.hello.com> wrote in message
news:356vljF4i904nU1@.individual.net...
>I currently have a main database server and want to implement a backup
>server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
server that replicates the data in my main server.
What is the best method of implementing this? I really don't know where to
start so even a pointer at some reading material would be helpful. Any
advice will be appreciated.Hi
Look up Log Shipping and Replication in BOL (or the Microsoft web site).
Those are your 2 built-in options.
Regards
Mike
"Michael" wrote:
> I currently have a main database server and want to implement a backup
> server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
>|||That depends on if you want to copy all of the data or a subset of the data.
If you want all the data and system objects and your destination database
can go offline while the transaction logs are applied, and is read only,
then log shipping is for you.
If you want only a subset of the data and don't care about the system
objects (like permissions, etc), need continualy accessability of the
destination database, and want to be able to update the destination database
use replication. Note that if you are not careful the updates you make on
the destination database can disrupt the replication process, but you can
partition your data so it doesn't.
"Michael" <michael@.hello.com> wrote in message
news:356vljF4i904nU1@.individual.net...
>I currently have a main database server and want to implement a backup
>server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
Backup server
I currently have a main database server and want to implement a backup
server that replicates the data in my main server.
What is the best method of implementing this? I really don't know where to
start so even a pointer at some reading material would be helpful. Any
advice will be appreciated.Hi
Look up Log Shipping and Replication in BOL (or the Microsoft web site).
Those are your 2 built-in options.
Regards
Mike
"Michael" wrote:
> I currently have a main database server and want to implement a backup
> server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
>|||That depends on if you want to copy all of the data or a subset of the data.
If you want all the data and system objects and your destination database
can go offline while the transaction logs are applied, and is read only,
then log shipping is for you.
If you want only a subset of the data and don't care about the system
objects (like permissions, etc), need continualy accessability of the
destination database, and want to be able to update the destination database
use replication. Note that if you are not careful the updates you make on
the destination database can disrupt the replication process, but you can
partition your data so it doesn't.
"Michael" <michael@.hello.com> wrote in message
news:356vljF4i904nU1@.individual.net...
>I currently have a main database server and want to implement a backup
>server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
server that replicates the data in my main server.
What is the best method of implementing this? I really don't know where to
start so even a pointer at some reading material would be helpful. Any
advice will be appreciated.Hi
Look up Log Shipping and Replication in BOL (or the Microsoft web site).
Those are your 2 built-in options.
Regards
Mike
"Michael" wrote:
> I currently have a main database server and want to implement a backup
> server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
>|||That depends on if you want to copy all of the data or a subset of the data.
If you want all the data and system objects and your destination database
can go offline while the transaction logs are applied, and is read only,
then log shipping is for you.
If you want only a subset of the data and don't care about the system
objects (like permissions, etc), need continualy accessability of the
destination database, and want to be able to update the destination database
use replication. Note that if you are not careful the updates you make on
the destination database can disrupt the replication process, but you can
partition your data so it doesn't.
"Michael" <michael@.hello.com> wrote in message
news:356vljF4i904nU1@.individual.net...
>I currently have a main database server and want to implement a backup
>server that replicates the data in my main server.
> What is the best method of implementing this? I really don't know where to
> start so even a pointer at some reading material would be helpful. Any
> advice will be appreciated.
>
Saturday, February 25, 2012
Backup of mirrored databases using TSM
Hi,
I currently have 2 mirrored servers and would like to implement a backup solution using an existing TSM server. The first thing that comes to mind is using the TSM client or Litespeed by Quest, but I'd like to know the effects of performing backups on principal and mirrored servers first.
Will using one of these products cause errors or problems should the backup client try to backup a mirrored database? Can anyone make any recommendations on the effects of using TSM client or Litespeed for a mirrored environment?
Thanks.
That depends on how you would like to do the restore process. The restore process will dictate how you may want to do your backups and not the other way around. In our case we just use the native SQL Server agent to generate the backup files and have TSM to pick up the backup files. This is a disadvantage if your backing up terrabytes of data. In this case, LightSpeed will help decrease backup time.|||Obviously, if you back up the principal while it is under heavy load, it will compete for resources. Backup tends to consume all available IO bandwidth, but not much CPU.
At the present time, you cannot back up a mirror database. Yes, I know, you want to, and we'll get to it, but not now.
Log backups will not interfere with mirroring as they would in a log-shipping environment, so that is not an issue.
Is there anything else you are concerned about?
|||Sorry for the delay in my reply. Both of your suggestions were helpful and will consider all my options.
Thanks.
Backup of mirrored databases using TSM
Hi,
I currently have 2 mirrored servers and would like to implement a backup solution using an existing TSM server. The first thing that comes to mind is using the TSM client or Litespeed by Quest, but I'd like to know the effects of performing backups on principal and mirrored servers first.
Will using one of these products cause errors or problems should the backup client try to backup a mirrored database? Can anyone make any recommendations on the effects of using TSM client or Litespeed for a mirrored environment?
Thanks.
That depends on how you would like to do the restore process. The restore process will dictate how you may want to do your backups and not the other way around. In our case we just use the native SQL Server agent to generate the backup files and have TSM to pick up the backup files. This is a disadvantage if your backing up terrabytes of data. In this case, LightSpeed will help decrease backup time.|||Obviously, if you back up the principal while it is under heavy load, it will compete for resources. Backup tends to consume all available IO bandwidth, but not much CPU.
At the present time, you cannot back up a mirror database. Yes, I know, you want to, and we'll get to it, but not now.
Log backups will not interfere with mirroring as they would in a log-shipping environment, so that is not an issue.
Is there anything else you are concerned about?
|||Sorry for the delay in my reply. Both of your suggestions were helpful and will consider all my options.
Thanks.
Backup of 9Gb Database
Hello all,
i was wandering if there are any documentation/suggestions on how to implement a backup that will not interrupt usage of database?
Basically we have a application that need to be available 24/7.
We have 2 servers, one is a primary, second using the log shipping function in case primary server dies. Howerver once a day when we perform full database backup system become non-responsive for 30-45 minutes.
Is there any ways around it? what are the best practice? We are thinking of creating the cluster of 2-3 SQL servers, however from what i have read, there is still going to be the same issue with backup on clusters.
Thanks.
i was wandering if there are any documentation/suggestions on how to implement a backup that will not interrupt usage of database?
Basically we have a application that need to be available 24/7.
We have 2 servers, one is a primary, second using the log shipping function in case primary server dies. Howerver once a day when we perform full database backup system become non-responsive for 30-45 minutes.
Is there any ways around it? what are the best practice? We are thinking of creating the cluster of 2-3 SQL servers, however from what i have read, there is still going to be the same issue with backup on clusters.
Thanks.
To limit the time, you can use tools like SQL Litespeed. This will bring the dump size down to about 25% to 30% of the original size. Also the amount of I/O will be less, because the OS has to read the same amount of I/O from the database, but less amount of I/O to the dump-file. Also the time needed to complete the dump is about 25% to 30% less than normal dumps.
Second option to consider is the snapshot option. Create a snapshot of the database and make a dump of the snapshot database (if that is possible)
|||Hi Kiryl,
MSSQL utilises "hot backups" that should not in any way cause interruption to service - most certainly not to the magnitude of 40 mins!
When you say "unresponsive", what form is this taking? Blocking, locking, cpu flat-line etc?
Cheers
Rob
Backup of 9Gb Database
Hello all,
i was wandering if there are any documentation/suggestions on how to implement a backup that will not interrupt usage of database?
Basically we have a application that need to be available 24/7.
We have 2 servers, one is a primary, second using the log shipping function in case primary server dies. Howerver once a day when we perform full database backup system become non-responsive for 30-45 minutes.
Is there any ways around it? what are the best practice? We are thinking of creating the cluster of 2-3 SQL servers, however from what i have read, there is still going to be the same issue with backup on clusters.
Thanks.
i was wandering if there are any documentation/suggestions on how to implement a backup that will not interrupt usage of database?
Basically we have a application that need to be available 24/7.
We have 2 servers, one is a primary, second using the log shipping function in case primary server dies. Howerver once a day when we perform full database backup system become non-responsive for 30-45 minutes.
Is there any ways around it? what are the best practice? We are thinking of creating the cluster of 2-3 SQL servers, however from what i have read, there is still going to be the same issue with backup on clusters.
Thanks.
To limit the time, you can use tools like SQL Litespeed. This will bring the dump size down to about 25% to 30% of the original size. Also the amount of I/O will be less, because the OS has to read the same amount of I/O from the database, but less amount of I/O to the dump-file. Also the time needed to complete the dump is about 25% to 30% less than normal dumps.
Second option to consider is the snapshot option. Create a snapshot of the database and make a dump of the snapshot database (if that is possible)
|||Hi Kiryl,
MSSQL utilises "hot backups" that should not in any way cause interruption to service - most certainly not to the magnitude of 40 mins!
When you say "unresponsive", what form is this taking? Blocking, locking, cpu flat-line etc?
Cheers
Rob
Subscribe to:
Posts (Atom)