Backup Software

Hi

We are getting ready to rollout a new system in the next few months and I have started to look at backup and recovery strategies for SQL Server 2005 on which this new system will be housed. The proposal is to by Veritas Backup Exec with the server this system will be housed on however my knowledge is "limited" to the backup and restore options available directly from SQL. I have been unable to find any opinion on using third party software to backup and restore SQL Server 2005 databases.

Can anyone help to give me an objective opinion on this subject. Should I simply use SQL Server and the tools it ships with or do these third-party applications make it easier?

Many thanks in advance of your help

Cheers

Danny

I find that using SQL's built in backup facility, backing up to a local drive, and then having a third party network backup product to move the backup to other locations/media is often the best choice.

|||I NEVER use backup agents to directly backup my SQL Server databases. The closest that I come is using SQL Litespeed at several customers so that we can take advantage of the compression and encryption features. Beyond that, I backup to disk and then use a utilty like Backup Exec to archive my backups to tape. I've simply had way too many very bad experiences in live disasters in the past to ever do backups any other way.|||

I have used redgate sql backup. this has more compresiion ratio , passowrd protected and backup will be encrypted.

However, SQL Server native backup also work for me lot of time. it will take more time than other tools but u can work with that

|||

I find SQL backup still the easiest (well, it could use lots of improvements) to use

We use Maintainence Plan to backup onto network file server on RAID5 (say we keep a weekly rotation)

and future plan is to use Veritas Backup Exec to backup those .BAK files (not sure how long the rotation will be, or if it's even necessary to backup SQL BAK files onto tape)

We did try Veritas SQL Agent as well, but due to network issues that's been halted for now

It wasn't too bad to use

|||

Backing-up to disk, using either SQL Server's native backups or a third-party backup tool, then backing-up from disk to tape is a great way to go if you have a sufficient time window. If you plan your backup regime properly you can keep several days' backups on disk and backup only the most recent backups to tape on a daily basis. This approach is beneficial when someone asks for a copy of a particular database from several days ago as you don't have to mess around recalling tapes etc...

Whether to use SQL Server's native backups or, instead, a third-party tool, such as Quest's SQL Litespeed or Red-Gate's SQL Backup, depends on whether you need to minimise the storage requirements of your backups and/or if you need to reduce the time taken to create the backup files. For instance, if you have only a couple of databases each of, say, 1GB in size then it probably isn't going to be worth investing in a third-party tool. If, on the otherhand, you have databases of, say, 200GB in size and you're backing-up to disk across a network then you'll probably see significant reductions in both backup file sizes and backup times if you use a third-party product that is capable of compression.

We use either SQL Server backups or SQL Litespeed backups, scheduled by SQL Agent, depending on the sizes of the databases on our servers - the decision is made on a server-by-server basis. We then use Backup Exec to backup the resultant backup files to tape. I must admit that I've never used Backup Exec to backup data straight from SQL Server, however to me it just doesn't 'feel' right doing it that way - anyway we're happy with the solution that we use so there's no need to change it. One other thing is that we've been using SQL Litespeed for around three years and performed literally hundreds of test restores and we have never had problems restoring databases from the compressed files (and, no, I don't work for Quest... ;) ).

Chris

|||Thank you all for your updates, most helpful!!!|||

The easiest way for me is to use a sql server backup program. The one I reccomend is www.4backuponline.com it will let you have a local copy and an online copy of you backup and it's really simple to use. You set it up once and choose when to run backups and it will run automatically and send daily emails with backup status.

I hope it helps,

|||I always do a quick backup of my project using Developer's Backup.|||

I do know that sqlbase a tape is not "allowed" to be ran over the database.

This is not the same situation for sql is it?

Backup Software

Hi

We are getting ready to rollout a new system in the next few months and I have started to look at backup and recovery strategies for SQL Server 2005 on which this new system will be housed. The proposal is to by Veritas Backup Exec with the server this system will be housed on however my knowledge is "limited" to the backup and restore options available directly from SQL. I have been unable to find any opinion on using third party software to backup and restore SQL Server 2005 databases.

Can anyone help to give me an objective opinion on this subject. Should I simply use SQL Server and the tools it ships with or do these third-party applications make it easier?

Many thanks in advance of your help

Cheers

Danny

I find that using SQL's built in backup facility, backing up to a local drive, and then having a third party network backup product to move the backup to other locations/media is often the best choice.

|||I NEVER use backup agents to directly backup my SQL Server databases. The closest that I come is using SQL Litespeed at several customers so that we can take advantage of the compression and encryption features. Beyond that, I backup to disk and then use a utilty like Backup Exec to archive my backups to tape. I've simply had way too many very bad experiences in live disasters in the past to ever do backups any other way.|||

I have used redgate sql backup. this has more compresiion ratio , passowrd protected and backup will be encrypted.

However, SQL Server native backup also work for me lot of time. it will take more time than other tools but u can work with that

|||

I find SQL backup still the easiest (well, it could use lots of improvements) to use

We use Maintainence Plan to backup onto network file server on RAID5 (say we keep a weekly rotation)

and future plan is to use Veritas Backup Exec to backup those .BAK files (not sure how long the rotation will be, or if it's even necessary to backup SQL BAK files onto tape)

We did try Veritas SQL Agent as well, but due to network issues that's been halted for now

It wasn't too bad to use

|||

Backing-up to disk, using either SQL Server's native backups or a third-party backup tool, then backing-up from disk to tape is a great way to go if you have a sufficient time window. If you plan your backup regime properly you can keep several days' backups on disk and backup only the most recent backups to tape on a daily basis. This approach is beneficial when someone asks for a copy of a particular database from several days ago as you don't have to mess around recalling tapes etc...

Whether to use SQL Server's native backups or, instead, a third-party tool, such as Quest's SQL Litespeed or Red-Gate's SQL Backup, depends on whether you need to minimise the storage requirements of your backups and/or if you need to reduce the time taken to create the backup files. For instance, if you have only a couple of databases each of, say, 1GB in size then it probably isn't going to be worth investing in a third-party tool. If, on the otherhand, you have databases of, say, 200GB in size and you're backing-up to disk across a network then you'll probably see significant reductions in both backup file sizes and backup times if you use a third-party product that is capable of compression.

We use either SQL Server backups or SQL Litespeed backups, scheduled by SQL Agent, depending on the sizes of the databases on our servers - the decision is made on a server-by-server basis. We then use Backup Exec to backup the resultant backup files to tape. I must admit that I've never used Backup Exec to backup data straight from SQL Server, however to me it just doesn't 'feel' right doing it that way - anyway we're happy with the solution that we use so there's no need to change it. One other thing is that we've been using SQL Litespeed for around three years and performed literally hundreds of test restores and we have never had problems restoring databases from the compressed files (and, no, I don't work for Quest... ;) ).

Chris

|||Thank you all for your updates, most helpful!!!|||

The easiest way for me is to use a sql server backup program. The one I reccomend is www.4backuponline.com it will let you have a local copy and an online copy of you backup and it's really simple to use. You set it up once and choose when to run backups and it will run automatically and send daily emails with backup status.

I hope it helps,

|||I always do a quick backup of my project using Developer's Backup.|||

I do know that sqlbase a tape is not "allowed" to be ran over the database.

This is not the same situation for sql is it?

Backup Software

Hi

We are getting ready to rollout a new system in the next few months and I have started to look at backup and recovery strategies for SQL Server 2005 on which this new system will be housed. The proposal is to by Veritas Backup Exec with the server this system will be housed on however my knowledge is "limited" to the backup and restore options available directly from SQL. I have been unable to find any opinion on using third party software to backup and restore SQL Server 2005 databases.

Can anyone help to give me an objective opinion on this subject. Should I simply use SQL Server and the tools it ships with or do these third-party applications make it easier?

Many thanks in advance of your help

Cheers

Danny

I find that using SQL's built in backup facility, backing up to a local drive, and then having a third party network backup product to move the backup to other locations/media is often the best choice.

|||I NEVER use backup agents to directly backup my SQL Server databases. The closest that I come is using SQL Litespeed at several customers so that we can take advantage of the compression and encryption features. Beyond that, I backup to disk and then use a utilty like Backup Exec to archive my backups to tape. I've simply had way too many very bad experiences in live disasters in the past to ever do backups any other way.|||

I have used redgate sql backup. this has more compresiion ratio , passowrd protected and backup will be encrypted.

However, SQL Server native backup also work for me lot of time. it will take more time than other tools but u can work with that

|||

I find SQL backup still the easiest (well, it could use lots of improvements) to use

We use Maintainence Plan to backup onto network file server on RAID5 (say we keep a weekly rotation)

and future plan is to use Veritas Backup Exec to backup those .BAK files (not sure how long the rotation will be, or if it's even necessary to backup SQL BAK files onto tape)

We did try Veritas SQL Agent as well, but due to network issues that's been halted for now

It wasn't too bad to use

|||

Backing-up to disk, using either SQL Server's native backups or a third-party backup tool, then backing-up from disk to tape is a great way to go if you have a sufficient time window. If you plan your backup regime properly you can keep several days' backups on disk and backup only the most recent backups to tape on a daily basis. This approach is beneficial when someone asks for a copy of a particular database from several days ago as you don't have to mess around recalling tapes etc...

Whether to use SQL Server's native backups or, instead, a third-party tool, such as Quest's SQL Litespeed or Red-Gate's SQL Backup, depends on whether you need to minimise the storage requirements of your backups and/or if you need to reduce the time taken to create the backup files. For instance, if you have only a couple of databases each of, say, 1GB in size then it probably isn't going to be worth investing in a third-party tool. If, on the otherhand, you have databases of, say, 200GB in size and you're backing-up to disk across a network then you'll probably see significant reductions in both backup file sizes and backup times if you use a third-party product that is capable of compression.

We use either SQL Server backups or SQL Litespeed backups, scheduled by SQL Agent, depending on the sizes of the databases on our servers - the decision is made on a server-by-server basis. We then use Backup Exec to backup the resultant backup files to tape. I must admit that I've never used Backup Exec to backup data straight from SQL Server, however to me it just doesn't 'feel' right doing it that way - anyway we're happy with the solution that we use so there's no need to change it. One other thing is that we've been using SQL Litespeed for around three years and performed literally hundreds of test restores and we have never had problems restoring databases from the compressed files (and, no, I don't work for Quest... ;) ).

Chris

|||Thank you all for your updates, most helpful!!!|||

The easiest way for me is to use a sql server backup program. The one I reccomend is www.4backuponline.com it will let you have a local copy and an online copy of you backup and it's really simple to use. You set it up once and choose when to run backups and it will run automatically and send daily emails with backup status.

I hope it helps,

|||I always do a quick backup of my project using Developer's Backup.|||

I do know that sqlbase a tape is not "allowed" to be ran over the database.

This is not the same situation for sql is it?

sql

Backup Software

Hi

We are getting ready to rollout a new system in the next few months and I have started to look at backup and recovery strategies for SQL Server 2005 on which this new system will be housed. The proposal is to by Veritas Backup Exec with the server this system will be housed on however my knowledge is "limited" to the backup and restore options available directly from SQL. I have been unable to find any opinion on using third party software to backup and restore SQL Server 2005 databases.

Can anyone help to give me an objective opinion on this subject. Should I simply use SQL Server and the tools it ships with or do these third-party applications make it easier?

Many thanks in advance of your help

Cheers

Danny

I find that using SQL's built in backup facility, backing up to a local drive, and then having a third party network backup product to move the backup to other locations/media is often the best choice.

|||I NEVER use backup agents to directly backup my SQL Server databases. The closest that I come is using SQL Litespeed at several customers so that we can take advantage of the compression and encryption features. Beyond that, I backup to disk and then use a utilty like Backup Exec to archive my backups to tape. I've simply had way too many very bad experiences in live disasters in the past to ever do backups any other way.|||

I have used redgate sql backup. this has more compresiion ratio , passowrd protected and backup will be encrypted.

However, SQL Server native backup also work for me lot of time. it will take more time than other tools but u can work with that

|||

I find SQL backup still the easiest (well, it could use lots of improvements) to use

We use Maintainence Plan to backup onto network file server on RAID5 (say we keep a weekly rotation)

and future plan is to use Veritas Backup Exec to backup those .BAK files (not sure how long the rotation will be, or if it's even necessary to backup SQL BAK files onto tape)

We did try Veritas SQL Agent as well, but due to network issues that's been halted for now

It wasn't too bad to use

|||

Backing-up to disk, using either SQL Server's native backups or a third-party backup tool, then backing-up from disk to tape is a great way to go if you have a sufficient time window. If you plan your backup regime properly you can keep several days' backups on disk and backup only the most recent backups to tape on a daily basis. This approach is beneficial when someone asks for a copy of a particular database from several days ago as you don't have to mess around recalling tapes etc...

Whether to use SQL Server's native backups or, instead, a third-party tool, such as Quest's SQL Litespeed or Red-Gate's SQL Backup, depends on whether you need to minimise the storage requirements of your backups and/or if you need to reduce the time taken to create the backup files. For instance, if you have only a couple of databases each of, say, 1GB in size then it probably isn't going to be worth investing in a third-party tool. If, on the otherhand, you have databases of, say, 200GB in size and you're backing-up to disk across a network then you'll probably see significant reductions in both backup file sizes and backup times if you use a third-party product that is capable of compression.

We use either SQL Server backups or SQL Litespeed backups, scheduled by SQL Agent, depending on the sizes of the databases on our servers - the decision is made on a server-by-server basis. We then use Backup Exec to backup the resultant backup files to tape. I must admit that I've never used Backup Exec to backup data straight from SQL Server, however to me it just doesn't 'feel' right doing it that way - anyway we're happy with the solution that we use so there's no need to change it. One other thing is that we've been using SQL Litespeed for around three years and performed literally hundreds of test restores and we have never had problems restoring databases from the compressed files (and, no, I don't work for Quest... ;) ).

Chris

|||Thank you all for your updates, most helpful!!!|||

The easiest way for me is to use a sql server backup program. The one I reccomend is www.4backuponline.com it will let you have a local copy and an online copy of you backup and it's really simple to use. You set it up once and choose when to run backups and it will run automatically and send daily emails with backup status.

I hope it helps,

|||I always do a quick backup of my project using Developer's Backup.|||

I do know that sqlbase a tape is not "allowed" to be ran over the database.

This is not the same situation for sql is it?

Backup Software

We are using SAN for the SQL Server 2000.
Someone mentions that since SQL Server is using cache during operation, when
we do the sanpshot of the SAN, the cache value has to be written to SAN. Is
it correct, what is the exact steps for this mechanism ?
Thanks"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:u0bsYJ5iGHA.4884@.TK2MSFTNGP03.phx.gbl...
> We are using SAN for the SQL Server 2000.
> Someone mentions that since SQL Server is using cache during operation,
> when we do the sanpshot of the SAN, the cache value has to be written to
> SAN. Is it correct,
Yes, that is correct. In effect the backup software requests that the
databse flush it's dirty pages to disk and prepare for the snapshot, then to
suspend writes while the snapshot is taken.

>what is the exact steps for this mechanism ?
VSS the Windows Volume Shadow Copy Service.
How Volume Shadow Copy Service Works
http://technet2.microsoft.com/Windo...3.mspx?mfr=true
That's how it should work. If your SAN software doesn't use VSS then you
should not use it to snapshot SQL Server databases.
David|||Dear David,
Thank you for your prompt reply.
Can you elaborate more about dirty pages ? Why they have to be flushed to
the disk ?
Rob
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ekh0FS5iGHA.4884@.TK2MSFTNGP03.phx.gbl...
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:u0bsYJ5iGHA.4884@.TK2MSFTNGP03.phx.gbl...
> Yes, that is correct. In effect the backup software requests that the
> databse flush it's dirty pages to disk and prepare for the snapshot, then
> to suspend writes while the snapshot is taken.
>
> VSS the Windows Volume Shadow Copy Service.
> How Volume Shadow Copy Service Works
> http://technet2.microsoft.com/Windo...3.mspx?mfr=true
>
> That's how it should work. If your SAN software doesn't use VSS then you
> should not use it to snapshot SQL Server databases.
> David
>|||"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:ei3PhW5iGHA.4512@.TK2MSFTNGP02.phx.gbl...
> Dear David,
> Thank you for your prompt reply.
> Can you elaborate more about dirty pages ? Why they have to be flushed to
> the disk ?
>
Dirty pages contain changes that a user has made to the database, but which
haven't been written to the data files yet. These changes have been
commited in the transaction logs, and they are real, complete, durable
transactions. If you don't flush these pages to disk before taking a
snapshot then you would loose data when restoring the database.
David

Backup Software

Hi all
I have just installed my first sql (2000) server & have now to think about
what backup software to use.
Can anyone recommend what backup software works best with sequal? I have
Arcserve & BackupExec on my other servers.
Regards
AaronI think the best recommendation is to use SQL Servers own backup function to
backup the database to a file. Then you can use what ever backup program to
backup the file.
Regards
Steen
Aaron S wrote:
> Hi all
> I have just installed my first sql (2000) server & have now to think
> about what backup software to use.
> Can anyone recommend what backup software works best with sequal? I
> have Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron|||You might find this useful:
http://www.microsoft.com/technet/pr...in/sqlops0.mspx
Andrew J. Kelly SQL MVP
"Aaron S" <aaron@.domain.com> wrote in message
news:OdnsfcnGFHA.588@.TK2MSFTNGP15.phx.gbl...
> Hi all
> I have just installed my first sql (2000) server & have now to think about
> what backup software to use.
> Can anyone recommend what backup software works best with sequal? I have
> Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron
>|||It could be a matter of personal preference as they both will do the job.
Base on my personal experience (with the 200+ servers at our location), I
would go for Arcserve. I find Arcserve more reliable but not faster than
BackupExec.
Here is an article which compares BackupExec 9.0, Netvault 7, Acrserve v9,
and tretrospect 6.5:
http://sartryck.idg.se/Art/Backup_5_NOK122003e.html
Sasan
Senior DBA
"Aaron S" wrote:

> Hi all
> I have just installed my first sql (2000) server & have now to think about
> what backup software to use.
> Can anyone recommend what backup software works best with sequal? I have
> Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron
>
>

Backup Software

We are using SAN for the SQL Server 2000.
Someone mentions that since SQL Server is using cache during operation, when
we do the sanpshot of the SAN, the cache value has to be written to SAN. Is
it correct, what is the exact steps for this mechanism ?
Thanks"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:u0bsYJ5iGHA.4884@.TK2MSFTNGP03.phx.gbl...
> We are using SAN for the SQL Server 2000.
> Someone mentions that since SQL Server is using cache during operation,
> when we do the sanpshot of the SAN, the cache value has to be written to
> SAN. Is it correct,
Yes, that is correct. In effect the backup software requests that the
databse flush it's dirty pages to disk and prepare for the snapshot, then to
suspend writes while the snapshot is taken.
>what is the exact steps for this mechanism ?
VSS the Windows Volume Shadow Copy Service.
How Volume Shadow Copy Service Works
http://technet2.microsoft.com/WindowsServer/en/Library/2b0d2457-b7d8-42c3-b6c9-59c145b7765f1033.mspx?mfr=true
That's how it should work. If your SAN software doesn't use VSS then you
should not use it to snapshot SQL Server databases.
David|||Dear David,
Thank you for your prompt reply.
Can you elaborate more about dirty pages ? Why they have to be flushed to
the disk ?
Rob
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ekh0FS5iGHA.4884@.TK2MSFTNGP03.phx.gbl...
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:u0bsYJ5iGHA.4884@.TK2MSFTNGP03.phx.gbl...
>> We are using SAN for the SQL Server 2000.
>> Someone mentions that since SQL Server is using cache during operation,
>> when we do the sanpshot of the SAN, the cache value has to be written to
>> SAN. Is it correct,
> Yes, that is correct. In effect the backup software requests that the
> databse flush it's dirty pages to disk and prepare for the snapshot, then
> to suspend writes while the snapshot is taken.
>>what is the exact steps for this mechanism ?
> VSS the Windows Volume Shadow Copy Service.
> How Volume Shadow Copy Service Works
> http://technet2.microsoft.com/WindowsServer/en/Library/2b0d2457-b7d8-42c3-b6c9-59c145b7765f1033.mspx?mfr=true
>
> That's how it should work. If your SAN software doesn't use VSS then you
> should not use it to snapshot SQL Server databases.
> David
>|||"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:ei3PhW5iGHA.4512@.TK2MSFTNGP02.phx.gbl...
> Dear David,
> Thank you for your prompt reply.
> Can you elaborate more about dirty pages ? Why they have to be flushed to
> the disk ?
>
Dirty pages contain changes that a user has made to the database, but which
haven't been written to the data files yet. These changes have been
commited in the transaction logs, and they are real, complete, durable
transactions. If you don't flush these pages to disk before taking a
snapshot then you would loose data when restoring the database.
David

Backup Software

Hi all
I have just installed my first sql (2000) server & have now to think about
what backup software to use.
Can anyone recommend what backup software works best with sequal? I have
Arcserve & BackupExec on my other servers.
Regards
AaronI think the best recommendation is to use SQL Servers own backup function to
backup the database to a file. Then you can use what ever backup program to
backup the file.
Regards
Steen
Aaron S wrote:
> Hi all
> I have just installed my first sql (2000) server & have now to think
> about what backup software to use.
> Can anyone recommend what backup software works best with sequal? I
> have Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron|||You might find this useful:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
--
Andrew J. Kelly SQL MVP
"Aaron S" <aaron@.domain.com> wrote in message
news:OdnsfcnGFHA.588@.TK2MSFTNGP15.phx.gbl...
> Hi all
> I have just installed my first sql (2000) server & have now to think about
> what backup software to use.
> Can anyone recommend what backup software works best with sequal? I have
> Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron
>|||It could be a matter of personal preference as they both will do the job.
Base on my personal experience (with the 200+ servers at our location), I
would go for Arcserve. I find Arcserve more reliable but not faster than
BackupExec.
Here is an article which compares BackupExec 9.0, Netvault 7, Acrserve v9,
and tretrospect 6.5:
http://sartryck.idg.se/Art/Backup_5_NOK122003e.html
Sasan
Senior DBA
"Aaron S" wrote:
> Hi all
> I have just installed my first sql (2000) server & have now to think about
> what backup software to use.
> Can anyone recommend what backup software works best with sequal? I have
> Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron
>
>sql

Backup Software

Hi all
I have just installed my first sql (2000) server & have now to think about
what backup software to use.
Can anyone recommend what backup software works best with sequal? I have
Arcserve & BackupExec on my other servers.
Regards
Aaron
I think the best recommendation is to use SQL Servers own backup function to
backup the database to a file. Then you can use what ever backup program to
backup the file.
Regards
Steen
Aaron S wrote:
> Hi all
> I have just installed my first sql (2000) server & have now to think
> about what backup software to use.
> Can anyone recommend what backup software works best with sequal? I
> have Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron
|||You might find this useful:
http://www.microsoft.com/technet/pro...n/sqlops0.mspx
Andrew J. Kelly SQL MVP
"Aaron S" <aaron@.domain.com> wrote in message
news:OdnsfcnGFHA.588@.TK2MSFTNGP15.phx.gbl...
> Hi all
> I have just installed my first sql (2000) server & have now to think about
> what backup software to use.
> Can anyone recommend what backup software works best with sequal? I have
> Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron
>
|||It could be a matter of personal preference as they both will do the job.
Base on my personal experience (with the 200+ servers at our location), I
would go for Arcserve. I find Arcserve more reliable but not faster than
BackupExec.
Here is an article which compares BackupExec 9.0, Netvault 7, Acrserve v9,
and tretrospect 6.5:
http://sartryck.idg.se/Art/Backup_5_NOK122003e.html
Sasan
Senior DBA
"Aaron S" wrote:

> Hi all
> I have just installed my first sql (2000) server & have now to think about
> what backup software to use.
> Can anyone recommend what backup software works best with sequal? I have
> Arcserve & BackupExec on my other servers.
>
> Regards
> Aaron
>
>

Backup requirements

Hi, This is confusing me - is there some reason why I "need" 3rd party
backup software to backup a single SQL Server 2000 database?
I do a full backup of a small (< 1Gb ) db each night to a hard disk on
another machine. I test this manually by doing a full restore from one
of the backups. I keep daily, wly, monthly copies.
I am now about to install an interal DAT drive on the SQL machine to do
this same plan, and will store tapes and manually test restoration from
tape the same way as above.
Any reason this scanario should require additional software, sql agents
licences etc ? Am I missing something because I am being told I need to
purchase additional software,agents,licences etc.
Thanks
hals_leftThird-party software isn't essential. SQL Server can backup direct to
tape anyway. You might still choose the software if you need some extra
features or if you find a different user-interface easier to use.
David Portas
SQL Server MVP
--|||If the tape unit is connected directly to the same server you do not need
any other software. If it is on a remote machine you will need a 3rd party
tool.
Andrew J. Kelly SQL MVP
"hals_left" <cc900630@.ntu.ac.uk> wrote in message
news:1125582021.374870.66900@.z14g2000cwz.googlegroups.com...
> Hi, This is confusing me - is there some reason why I "need" 3rd party
> backup software to backup a single SQL Server 2000 database?
> I do a full backup of a small (< 1Gb ) db each night to a hard disk on
> another machine. I test this manually by doing a full restore from one
> of the backups. I keep daily, wly, monthly copies.
> I am now about to install an interal DAT drive on the SQL machine to do
> this same plan, and will store tapes and manually test restoration from
> tape the same way as above.
> Any reason this scanario should require additional software, sql agents
> licences etc ? Am I missing something because I am being told I need to
> purchase additional software,agents,licences etc.
> Thanks
> hals_left
>|||I think for a small project the SQL tools are sufficient and the DAT
drive will be connected to the SQL machine.
The other thing the salesperson has said is that my plan wont "flush"
the transaction logs - and this is a big problem. Maybe later on I
will use differential backups etc , but for the short term I am not
backing up the transaction logs at all but doing a full daily backup.
Does this overwrite the transaction logs so they do not need flushing ?
Is this "flushing" the logs something to consider when doing full
backups ?
Last question - What is the appropriate owner for the backup job ? sa
or the the Windows administrator account, or some other account with
fewer privelages?
Thanks.|||I don't know what he meant by "flush the transaction logs"? If you are only
doing FULL backups you need to place the recovery mode to SIMPLE and it will
automatically truncate the log files. If you want to recover up to a point
in time you need to be in FULL recovery mode. But then you need to do
regular log backups as well. You should read the topics in BooksOnLIne for
Backup and Restore and this link may be helpful as well:
http://www.microsoft.com/technet/pr...in/sqlops0.mspx
Operations Guide
As for what account it depends. I am not sure if the Tape unit needs a
Domain account or not (i doubt it) but if you backup to a remote machine you
definitely need a domain account. The account that Sql Server runs under is
what counts for backups.
Andrew J. Kelly SQL MVP
"hals_left" <cc900630@.ntu.ac.uk> wrote in message
news:1125649300.186451.256910@.g43g2000cwa.googlegroups.com...
>I think for a small project the SQL tools are sufficient and the DAT
> drive will be connected to the SQL machine.
> The other thing the salesperson has said is that my plan wont "flush"
> the transaction logs - and this is a big problem. Maybe later on I
> will use differential backups etc , but for the short term I am not
> backing up the transaction logs at all but doing a full daily backup.
> Does this overwrite the transaction logs so they do not need flushing ?
>
> Is this "flushing" the logs something to consider when doing full
> backups ?
> Last question - What is the appropriate owner for the backup job ? sa
> or the the Windows administrator account, or some other account with
> fewer privelages?
> Thanks.
>

Backup question: SQL 7.5 vs. SQL 2000

Wondering if SQL 2000 offers any compression of logical backups vs. no software compression in SQL 7.5. I've been asked to evaluate a 3rd party tool that compresses SQL 7.5 backups nicely, but this tool does not allow concatenating all databases into a single logical device file. I'm thinking I won't recommend the tool if SQL 2000 does compression on the fly as we will be upgrading sometime over the next handful of months.

TIAwhat tool are you referring to? sqllitespeed? and why would you need to append to the device? so that when you really need it you can't find it or it became corrupt and you consequently cannot recover anything?

sql2k does not compress, but m$ adopted sqllitespeed just for that purpose, as well as because it offers encryption (something that everybody is concerned about nowadays)

Backup of SQL DB with Veritas Agents

Help!
We just upgraded to version 10d of the Veritas/Symantec software - part of
upgrade was to update the remote backup exec agent that is used to backup SQ
L
db's.
This is the event log entries for the job that fails.
Source MSSQL Server
Event ID 17055
18210 :
BackupVirtualDeviceSet::Initialize: Open failure on backup device
'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'. Operating system error
-2147024891(Access is denied.).
---
Source Backup Exec
Event ID 57859
An error occurred while executing the following query: "BACKUP DATABASE
[master] TO virtual_device =
'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'".
On server: "CD_PA".
SQL error number: "0BC5".
SQL error message: "Backup or restore operation terminating abnormally.
".
For more information, click the following link:
http://eventlookup.veritas.com/even...entLookup.jhtml
The jobs worked until we upgraded... Veritas wants me to make all these
changes... we are only running SQL7.0 no SQL 2000
Anybody have this issue...and had any luck getting it resolved withou
upgrading SQL?
Please advise.
Thanks.
-John
Citigate Cunningham HelpdeskHi
Have you checked account which is running veritas to see whether it has
privileges?
John
"Citigate Cunningham Helpdesk" wrote:

> Help!
> We just upgraded to version 10d of the Veritas/Symantec software - part of
> upgrade was to update the remote backup exec agent that is used to backup
SQL
> db's.
> This is the event log entries for the job that fails.
> Source MSSQL Server
> Event ID 17055
> 18210 :
> BackupVirtualDeviceSet::Initialize: Open failure on backup device
> 'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'. Operating system error
> -2147024891(Access is denied.).
>
> ---
> Source Backup Exec
> Event ID 57859
> An error occurred while executing the following query: "BACKUP DATABASE
> [master] TO virtual_device =
> 'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'".
> On server: "CD_PA".
> SQL error number: "0BC5".
> SQL error message: "Backup or restore operation terminating abnormally.
> ".
> For more information, click the following link:
> http://eventlookup.veritas.com/even...entLookup.jhtml
> The jobs worked until we upgraded... Veritas wants me to make all these
> changes... we are only running SQL7.0 no SQL 2000
> Anybody have this issue...and had any luck getting it resolved withou
> upgrading SQL?
> Please advise.
> Thanks.
> -John
> Citigate Cunningham Helpdesk
>|||John,
http://support.microsoft.com/defaul...kb;en-us;280759
Veritas has me trying renaming some of the dll's ... I did update the
Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
did not work on the NT40 box.
There were some additonal dlls that it recommended that also get copied
over... this is our finance server... and I don't want to mess it up.
Prior to the upgrade.... from 9.x to 10d it worked fine.
-John
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked account which is running veritas to see whether it has
> privileges?
> John
> "Citigate Cunningham Helpdesk" wrote:
>|||Hi
If you have the disc space you may want to do away with the agent and just
back up to disc. Then you can schedule the normal file backup to put this
onto tape. Unless absolutly necessary I try an avoid using the agents as the
y
can cause so many issues like yours!
John
"Citigate Cunningham Helpdesk" wrote:
[vbcol=seagreen]
> John,
> http://support.microsoft.com/defaul...kb;en-us;280759
> Veritas has me trying renaming some of the dll's ... I did update the
> Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
> did not work on the NT40 box.
> There were some additonal dlls that it recommended that also get copied
> over... this is our finance server... and I don't want to mess it up.
> Prior to the upgrade.... from 9.x to 10d it worked fine.
> -John
> "John Bell" wrote:
>

Backup of SQL DB with Veritas Agents

Help!
We just upgraded to version 10d of the Veritas/Symantec software - part of
upgrade was to update the remote backup exec agent that is used to backup SQL
db's.
This is the event log entries for the job that fails.
Source MSSQL Server
Event ID 17055
18210 :
BackupVirtualDeviceSet::Initialize: Open failure on backup device
'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
-2147024891(Access is denied.).
---
Source Backup Exec
Event ID 57859
An error occurred while executing the following query: "BACKUP DATABASE
[master] TO virtual_device = 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
On server: "CD_PA".
SQL error number: "0BC5".
SQL error message: "Backup or restore operation terminating abnormally.
".
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
The jobs worked until we upgraded... Veritas wants me to make all these
changes... we are only running SQL7.0 no SQL 2000
Anybody have this issue...and had any luck getting it resolved withou
upgrading SQL?
Please advise.
Thanks.
-John
Citigate Cunningham HelpdeskHi
Have you checked account which is running veritas to see whether it has
privileges?
John
"Citigate Cunningham Helpdesk" wrote:
> Help!
> We just upgraded to version 10d of the Veritas/Symantec software - part of
> upgrade was to update the remote backup exec agent that is used to backup SQL
> db's.
> This is the event log entries for the job that fails.
> Source MSSQL Server
> Event ID 17055
> 18210 :
> BackupVirtualDeviceSet::Initialize: Open failure on backup device
> 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> -2147024891(Access is denied.).
>
> ---
> Source Backup Exec
> Event ID 57859
> An error occurred while executing the following query: "BACKUP DATABASE
> [master] TO virtual_device => 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> On server: "CD_PA".
> SQL error number: "0BC5".
> SQL error message: "Backup or restore operation terminating abnormally.
> ".
> For more information, click the following link:
> http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> The jobs worked until we upgraded... Veritas wants me to make all these
> changes... we are only running SQL7.0 no SQL 2000
> Anybody have this issue...and had any luck getting it resolved withou
> upgrading SQL?
> Please advise.
> Thanks.
> -John
> Citigate Cunningham Helpdesk
>|||John,
http://support.microsoft.com/default.aspx?scid=kb;en-us;280759
Veritas has me trying renaming some of the dll's ... I did update the
Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
did not work on the NT40 box.
There were some additonal dlls that it recommended that also get copied
over... this is our finance server... and I don't want to mess it up.
Prior to the upgrade.... from 9.x to 10d it worked fine.
-John
"John Bell" wrote:
> Hi
> Have you checked account which is running veritas to see whether it has
> privileges?
> John
> "Citigate Cunningham Helpdesk" wrote:
> > Help!
> >
> > We just upgraded to version 10d of the Veritas/Symantec software - part of
> > upgrade was to update the remote backup exec agent that is used to backup SQL
> > db's.
> >
> > This is the event log entries for the job that fails.
> >
> > Source MSSQL Server
> > Event ID 17055
> > 18210 :
> > BackupVirtualDeviceSet::Initialize: Open failure on backup device
> > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> > -2147024891(Access is denied.).
> >
> >
> > ---
> >
> > Source Backup Exec
> > Event ID 57859
> >
> > An error occurred while executing the following query: "BACKUP DATABASE
> > [master] TO virtual_device => > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> > On server: "CD_PA".
> > SQL error number: "0BC5".
> > SQL error message: "Backup or restore operation terminating abnormally.
> > ".
> >
> > For more information, click the following link:
> > http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> >
> > The jobs worked until we upgraded... Veritas wants me to make all these
> > changes... we are only running SQL7.0 no SQL 2000
> >
> > Anybody have this issue...and had any luck getting it resolved withou
> > upgrading SQL?
> >
> > Please advise.
> >
> > Thanks.
> >
> > -John
> > Citigate Cunningham Helpdesk
> >|||Hi
If you have the disc space you may want to do away with the agent and just
back up to disc. Then you can schedule the normal file backup to put this
onto tape. Unless absolutly necessary I try an avoid using the agents as they
can cause so many issues like yours!
John
"Citigate Cunningham Helpdesk" wrote:
> John,
> http://support.microsoft.com/default.aspx?scid=kb;en-us;280759
> Veritas has me trying renaming some of the dll's ... I did update the
> Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
> did not work on the NT40 box.
> There were some additonal dlls that it recommended that also get copied
> over... this is our finance server... and I don't want to mess it up.
> Prior to the upgrade.... from 9.x to 10d it worked fine.
> -John
> "John Bell" wrote:
> > Hi
> >
> > Have you checked account which is running veritas to see whether it has
> > privileges?
> >
> > John
> >
> > "Citigate Cunningham Helpdesk" wrote:
> >
> > > Help!
> > >
> > > We just upgraded to version 10d of the Veritas/Symantec software - part of
> > > upgrade was to update the remote backup exec agent that is used to backup SQL
> > > db's.
> > >
> > > This is the event log entries for the job that fails.
> > >
> > > Source MSSQL Server
> > > Event ID 17055
> > > 18210 :
> > > BackupVirtualDeviceSet::Initialize: Open failure on backup device
> > > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> > > -2147024891(Access is denied.).
> > >
> > >
> > > ---
> > >
> > > Source Backup Exec
> > > Event ID 57859
> > >
> > > An error occurred while executing the following query: "BACKUP DATABASE
> > > [master] TO virtual_device => > > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> > > On server: "CD_PA".
> > > SQL error number: "0BC5".
> > > SQL error message: "Backup or restore operation terminating abnormally.
> > > ".
> > >
> > > For more information, click the following link:
> > > http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> > >
> > > The jobs worked until we upgraded... Veritas wants me to make all these
> > > changes... we are only running SQL7.0 no SQL 2000
> > >
> > > Anybody have this issue...and had any luck getting it resolved withou
> > > upgrading SQL?
> > >
> > > Please advise.
> > >
> > > Thanks.
> > >
> > > -John
> > > Citigate Cunningham Helpdesk
> > >

Backup Microsoft SQL server desktop engine 8.00.761

Dear Sirs.
I'm not an expert on SQL, and have a few questions. A friend has installed a
software using Microsoft SQL server desktop engine 8.00.761, and i'm trying
to help him setting up a backup to disk for him. The software using sql is a
commercial, with very poor builtin backup system. It's an economy software,
and You need to make backup of each firm manually 1 by 1, and when You have
600+ companies this isn't acceptable. I'd like to set up an automatical
backup (Full) to disk each night, i've set up a rotating swapping of external
disk system for him. I've noticed that when ever he adds a new company to
the SQL database, a new table under USER is added. Any tips on any simple
software that can be used? Does Microsoft SQL server desktop engine 8.00.761
have any built in backup features? Can i install to Microsoft SQL Express
2005 and try to get the SQL database working with that?
I tried a software called DMT SQL Backup manager 2.3.1.0 but it took 19
minutes to backup a database consisting of 570MB data, is this normal?
With regards
Erling HerstadPlease try Using
Litespeed and SQL backtrack from BMC software.
Thanks
Ajay Rengunthwar
MCTS
On Feb 26, 4:38=A0am, Erling Herstad
<ErlingHers...@.discussions.microsoft.com> wrote:
> Dear Sirs.
> I'm not an expert on SQL, and have a few questions. A friend has installed= a
> software using Microsoft SQL server desktop engine =A0 8.00.761, and i'm t=rying
> to help him setting up a backup to disk for him. The software using sql is= a
> commercial, with very poor builtin backup system. It's an economy software=,
> and You need to make backup of each firm manually 1 by 1, and when You hav=e
> 600+ companies this isn't acceptable. I'd like to set up an automatical
> backup (Full) to disk each night, i've set up a rotating swapping of exter=nal
> disk system for him. =A0I've noticed that when ever he adds a new company =to
> the SQL database, a new table under USER is added. Any tips on any simple
> software that can be used? Does Microsoft SQL server desktop engine 8.00.7=61
> have any built in backup features? Can i install to Microsoft SQL Express
> 2005 and try to get the SQL database working with that?
> I tried a software called DMT SQL Backup manager 2.3.1.0 but it took 19
> minutes to backup a database consisting of 570MB data, is this normal?
> With regards
> Erling Herstad|||You can use the the native backup commands. You can install the client tools
and connect to it to use the GUI to set up jobs. Also, you ought apply SP4.
That is the RTM version and is open to the slammer worm.
--
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Erling Herstad" <ErlingHerstad@.discussions.microsoft.com> wrote in message
news:6E7DC668-A458-463C-8AF7-D54C3A842410@.microsoft.com...
> Dear Sirs.
> I'm not an expert on SQL, and have a few questions. A friend has installed
> a
> software using Microsoft SQL server desktop engine 8.00.761, and i'm
> trying
> to help him setting up a backup to disk for him. The software using sql is
> a
> commercial, with very poor builtin backup system. It's an economy
> software,
> and You need to make backup of each firm manually 1 by 1, and when You
> have
> 600+ companies this isn't acceptable. I'd like to set up an automatical
> backup (Full) to disk each night, i've set up a rotating swapping of
> external
> disk system for him. I've noticed that when ever he adds a new company to
> the SQL database, a new table under USER is added. Any tips on any simple
> software that can be used? Does Microsoft SQL server desktop engine
> 8.00.761
> have any built in backup features? Can i install to Microsoft SQL Express
> 2005 and try to get the SQL database working with that?
> I tried a software called DMT SQL Backup manager 2.3.1.0 but it took 19
> minutes to backup a database consisting of 570MB data, is this normal?
> With regards
> Erling Herstad
>|||Hi.
i'll have a look into the software you suggested.
"Ajay Rengunthwar" wrote:
> Please try Using
> Litespeed and SQL backtrack from BMC software.
>
> Thanks
> Ajay Rengunthwar
> MCTS
> On Feb 26, 4:38 am, Erling Herstad
> <ErlingHers...@.discussions.microsoft.com> wrote:
> > Dear Sirs.
> >
> > I'm not an expert on SQL, and have a few questions. A friend has installed a
> > software using Microsoft SQL server desktop engine 8.00.761, and i'm trying
> > to help him setting up a backup to disk for him. The software using sql is a
> > commercial, with very poor builtin backup system. It's an economy software,
> > and You need to make backup of each firm manually 1 by 1, and when You have
> > 600+ companies this isn't acceptable. I'd like to set up an automatical
> > backup (Full) to disk each night, i've set up a rotating swapping of external
> > disk system for him. I've noticed that when ever he adds a new company to
> > the SQL database, a new table under USER is added. Any tips on any simple
> > software that can be used? Does Microsoft SQL server desktop engine 8.00.761
> > have any built in backup features? Can i install to Microsoft SQL Express
> > 2005 and try to get the SQL database working with that?
> > I tried a software called DMT SQL Backup manager 2.3.1.0 but it took 19
> > minutes to backup a database consisting of 570MB data, is this normal?
> >
> > With regards
> > Erling Herstad
>|||Hi.
Do You have a link for the Client tools? And a link to SP4?
"jason" wrote:
> You can use the the native backup commands. You can install the client tools
> and connect to it to use the GUI to set up jobs. Also, you ought apply SP4.
> That is the RTM version and is open to the slammer worm.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
>
> "Erling Herstad" <ErlingHerstad@.discussions.microsoft.com> wrote in message
> news:6E7DC668-A458-463C-8AF7-D54C3A842410@.microsoft.com...
> > Dear Sirs.
> >
> > I'm not an expert on SQL, and have a few questions. A friend has installed
> > a
> > software using Microsoft SQL server desktop engine 8.00.761, and i'm
> > trying
> > to help him setting up a backup to disk for him. The software using sql is
> > a
> > commercial, with very poor builtin backup system. It's an economy
> > software,
> > and You need to make backup of each firm manually 1 by 1, and when You
> > have
> > 600+ companies this isn't acceptable. I'd like to set up an automatical
> > backup (Full) to disk each night, i've set up a rotating swapping of
> > external
> > disk system for him. I've noticed that when ever he adds a new company to
> > the SQL database, a new table under USER is added. Any tips on any simple
> > software that can be used? Does Microsoft SQL server desktop engine
> > 8.00.761
> > have any built in backup features? Can i install to Microsoft SQL Express
> > 2005 and try to get the SQL database working with that?
> > I tried a software called DMT SQL Backup manager 2.3.1.0 but it took 19
> > minutes to backup a database consisting of 570MB data, is this normal?
> >
> > With regards
> > Erling Herstad
> >
>