DR strategies

We have a large database for production and need to come up with a solution
for Disaster Recovery.
Performing tasks such as a full backup and transaction backups, then
shipping over across country is okay during initial setup. But long term it
will not be possible to ship a full backup across. Transactional backups
shipping and restoring to a read-only instance would be okay; but, occasiona
l
full backups of the production system would be needed for development teams.
So this would cause a problem for the DR system.
What are the different options either via a Microsoft solution or a 3rd part
y?Tom,
For MS solutions you might want to have a look at
http://support.microsoft.com/defaul...b;en-us;822400.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:9D54441D-E203-4544-8F37-6EDAFE7DCC79@.microsoft.com...
> We have a large database for production and need to come up with a
solution
> for Disaster Recovery.
> Performing tasks such as a full backup and transaction backups, then
> shipping over across country is okay during initial setup. But long term
it
> will not be possible to ship a full backup across. Transactional backups
> shipping and restoring to a read-only instance would be okay; but,
occasional
> full backups of the production system would be needed for development
teams.
> So this would cause a problem for the DR system.
> What are the different options either via a Microsoft solution or a 3rd
party?sql

DR strategies

We have a large database for production and need to come up with a solution
for Disaster Recovery.
Performing tasks such as a full backup and transaction backups, then
shipping over across country is okay during initial setup. But long term it
will not be possible to ship a full backup across. Transactional backups
shipping and restoring to a read-only instance would be okay; but, occasional
full backups of the production system would be needed for development teams.
So this would cause a problem for the DR system.
What are the different options either via a Microsoft solution or a 3rd party?Tom,
For MS solutions you might want to have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;822400.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:9D54441D-E203-4544-8F37-6EDAFE7DCC79@.microsoft.com...
> We have a large database for production and need to come up with a
solution
> for Disaster Recovery.
> Performing tasks such as a full backup and transaction backups, then
> shipping over across country is okay during initial setup. But long term
it
> will not be possible to ship a full backup across. Transactional backups
> shipping and restoring to a read-only instance would be okay; but,
occasional
> full backups of the production system would be needed for development
teams.
> So this would cause a problem for the DR system.
> What are the different options either via a Microsoft solution or a 3rd
party?

DR strategies

We have a large database for production and need to come up with a solution
for Disaster Recovery.
Performing tasks such as a full backup and transaction backups, then
shipping over across country is okay during initial setup. But long term it
will not be possible to ship a full backup across. Transactional backups
shipping and restoring to a read-only instance would be okay; but, occasional
full backups of the production system would be needed for development teams.
So this would cause a problem for the DR system.
What are the different options either via a Microsoft solution or a 3rd party?
Tom,
For MS solutions you might want to have a look at
http://support.microsoft.com/default...;en-us;822400.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:9D54441D-E203-4544-8F37-6EDAFE7DCC79@.microsoft.com...
> We have a large database for production and need to come up with a
solution
> for Disaster Recovery.
> Performing tasks such as a full backup and transaction backups, then
> shipping over across country is okay during initial setup. But long term
it
> will not be possible to ship a full backup across. Transactional backups
> shipping and restoring to a read-only instance would be okay; but,
occasional
> full backups of the production system would be needed for development
teams.
> So this would cause a problem for the DR system.
> What are the different options either via a Microsoft solution or a 3rd
party?

Downloads becoming corrupt while use FTP Task

I have a Package that downloads apprx 15 data archives from an FTP site using FTP Tasks.

My problem is that the data contained within these archives (.Z) are becoming corrupt after download/extracting. I have isolated the problem to the FTP File Task by manually downloading the archives myself from IE's built-in FTP client and disabling the downloads in the Control Flow. The Control Flow will then execute the extracting script and continue without any problems.

If I run the Package with the FTP Tasks enabled it will get to a random spot in the validation (I haven't been able to see any consistency with where it errors) of the flat files and error with either a truncation error or a (don't remember exactly what it was) error that talks about an unexpected end in the file. I believe this is because the data has become corrupt and has started skipping/excluding columns. I have opened the flat file and examined it, and sure enough, the data at the end seems to just end.

I have tried setting the FTP Connection to Use Passive Mode in the config file - doesn't work.

So, my question is: Has anyone encountered similar problems? If so, what did you do to fix the problem? I'd really like to use the FTP Task rather than reinventing it with a custom script.Are you downloading these files sequentially to the same local file? If yes, add File System Task that deletes the destination (local) file before downloading to it.

There is a known issue with FTP task - it does not delete the destination file before overwriting it with content of new file. So if one of the files is smaller than than previous one - the file will have garbage from older file in the end. This problem will be corrected by SP2, and the workaround is to delete the local file or use unique local names.sql