Backing up on windows compressed drive

Colleagues,
Does anybody have experience with backing up of MS SQL database on MS
Windows compressed drive? As for me, it is a good possibility to resolve disk
space problems and save some money. I know, that option of compressed backup
will be build in MS SQL 2008 and some 3-rd party products has the
functionality. But what about simple MS SQL backup on Windows compressed
drive?I asked this question a while ago and basically got blasted :)
- Don't let your hardware determin your business requirments.
- You won't actually know how much space is left and might fill the drive.
- backups and restores will table longer - mainly an issue with restores.
And I only was thinking about it for a dev system.
Still, depending on the compisition of your database, you could save a lot.
"Dmitrij Siemieniako" <Dmitrij Siemieniako@.discussions.microsoft.com> wrote
in message news:B0303671-D53F-49F7-8F01-ABD501AF8F17@.microsoft.com...
> Colleagues,
> Does anybody have experience with backing up of MS SQL database on MS
> Windows compressed drive? As for me, it is a good possibility to resolve
> disk
> space problems and save some money. I know, that option of compressed
> backup
> will be build in MS SQL 2008 and some 3-rd party products has the
> functionality. But what about simple MS SQL backup on Windows compressed
> drive?
>|||"Jay" <spam@.nospam.org> wrote in message
news:uTFvrDt9HHA.4880@.TK2MSFTNGP03.phx.gbl...
>I asked this question a while ago and basically got blasted :)
> - Don't let your hardware determin your business requirments.
> - You won't actually know how much space is left and might fill the drive.
> - backups and restores will table longer - mainly an issue with restores.
Depends on what he's suggesting. It's not 100% clear to me.
If he means to run the DB on a compressed drive, then no, that's a bad idea.
If he means backups TO a compressed drive, that's less risky.
And depending on many factors, backups/restores may in fact be faster, much
faster.
He can also look into some of the 3rd party backup solutions that compress
as they backup.
Very handy, especially for larger databases.
> And I only was thinking about it for a dev system.
> Still, depending on the compisition of your database, you could save a
> lot.
> "Dmitrij Siemieniako" <Dmitrij Siemieniako@.discussions.microsoft.com>
> wrote in message
> news:B0303671-D53F-49F7-8F01-ABD501AF8F17@.microsoft.com...
>> Colleagues,
>> Does anybody have experience with backing up of MS SQL database on MS
>> Windows compressed drive? As for me, it is a good possibility to resolve
>> disk
>> space problems and save some money. I know, that option of compressed
>> backup
>> will be build in MS SQL 2008 and some 3-rd party products has the
>> functionality. But what about simple MS SQL backup on Windows compressed
>> drive?
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Well, he did say "backing up"
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:e7tzrYu9HHA.1484@.TK2MSFTNGP06.phx.gbl...
> "Jay" <spam@.nospam.org> wrote in message
> news:uTFvrDt9HHA.4880@.TK2MSFTNGP03.phx.gbl...
>>I asked this question a while ago and basically got blasted :)
>> - Don't let your hardware determin your business requirments.
>> - You won't actually know how much space is left and might fill the
>> drive.
>> - backups and restores will table longer - mainly an issue with restores.
> Depends on what he's suggesting. It's not 100% clear to me.
> If he means to run the DB on a compressed drive, then no, that's a bad
> idea.
> If he means backups TO a compressed drive, that's less risky.
> And depending on many factors, backups/restores may in fact be faster,
> much faster.
> He can also look into some of the 3rd party backup solutions that compress
> as they backup.
> Very handy, especially for larger databases.
>
>> And I only was thinking about it for a dev system.
>> Still, depending on the compisition of your database, you could save a
>> lot.
>> "Dmitrij Siemieniako" <Dmitrij Siemieniako@.discussions.microsoft.com>
>> wrote in message
>> news:B0303671-D53F-49F7-8F01-ABD501AF8F17@.microsoft.com...
>> Colleagues,
>> Does anybody have experience with backing up of MS SQL database on MS
>> Windows compressed drive? As for me, it is a good possibility to resolve
>> disk
>> space problems and save some money. I know, that option of compressed
>> backup
>> will be build in MS SQL 2008 and some 3-rd party products has the
>> functionality. But what about simple MS SQL backup on Windows compressed
>> drive?
>>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>|||Thanks a lot, Jay. So, I'll try to move my backups on compressed drive.
Regards.
Dmitruj

backing up

we want to back up our new point of sale system with is
running a sequel server. on to a zip drive software does
not come with any instructions for how to do so any ideas?
Personally, I would probably try to backup to disk first, and then =
backup to your removable drive.
Either way, something like this should work for you, just change the =
drive letter.
Test this from Query Analyzer. When it works create a scheduled job. =
You will also want to backup msdb as well as your user database(s). =
Make sure that you backup each database to a separate file.
BACKUP DATABASE master TO DISK =3D 'c:\master.bak' WITH INIT
go
EXEC master..xp_cmdshell 'copy c:\master.bak x:\master.bak'
GO
--=20
Keith
"chris" <anonymous@.discussions.microsoft.com> wrote in message =
news:b80c01c43791$fc4f2f50$a001280a@.phx.gbl...
> we want to back up our new point of sale system with is=20
> running a sequel server. on to a zip drive software does=20
> not come with any instructions for how to do so any ideas?

backing up

we want to back up our new point of sale system with is
running a sequel server. on to a zip drive software does
not come with any instructions for how to do so any ideas?Personally, I would probably try to backup to disk first, and then =
backup to your removable drive.
Either way, something like this should work for you, just change the =
drive letter.
Test this from Query Analyzer. When it works create a scheduled job. =
You will also want to backup msdb as well as your user database(s). =
Make sure that you backup each database to a separate file.
BACKUP DATABASE master TO DISK =3D 'c:\master.bak' WITH INIT
go
EXEC master..xp_cmdshell 'copy c:\master.bak x:\master.bak'
GO
--=20
Keith
"chris" <anonymous@.discussions.microsoft.com> wrote in message =
news:b80c01c43791$fc4f2f50$a001280a@.phx.gbl...
> we want to back up our new point of sale system with is=20
> running a sequel server. on to a zip drive software does=20
> not come with any instructions for how to do so any ideas?

backing up

we want to back up our new point of sale system with is
running a sequel server. on to a zip drive software does
not come with any instructions for how to do so any ideas?Personally, I would probably try to backup to disk first, and then =backup to your removable drive.
Either way, something like this should work for you, just change the =drive letter.
Test this from Query Analyzer. When it works create a scheduled job. =You will also want to backup msdb as well as your user database(s). =Make sure that you backup each database to a separate file.
BACKUP DATABASE master TO DISK =3D 'c:\master.bak' WITH INIT
go
EXEC master..xp_cmdshell 'copy c:\master.bak x:\master.bak'
GO
-- Keith
"chris" <anonymous@.discussions.microsoft.com> wrote in message =news:b80c01c43791$fc4f2f50$a001280a@.phx.gbl...
> we want to back up our new point of sale system with is > running a sequel server. on to a zip drive software does > not come with any instructions for how to do so any ideas?

Backend generate and save the report to local drive?

Hi,
Any ideas on how to automatically generate and save the report to local
server drive backend when user click on certain link on the application?
The user do not have to render and display the report in frontend or click
on save button when prompted? The system should not prompt user for any
action instead.
Thanks in advance for any suggestion.Hi,
you can call the WebService of reporting Services (with optional
additional parameters, get the byte[] from the render method and save
this in a file on your network share of choice. That can all happen
behind the scenes and in addition if you want to asynchronously.
HTH, Jens K. Suessmeyer.
--
http://www.sqlserver2005.de
--

Back Up question

I currently have my database backed up to the same physical drive where the data resides. In the event of drive failure, I would lose everything. Due to space considerations on a tape, I was wondering if I can copy only the database backup file (.BAK) and not the transaction log backup (.TRN). Can I go ahead with this approach if I do not want point-in-time recovery and I am satisfied with only what resides on .BAK file? Will I able to restore the database from the tape if the tape contains only the (.BAK) file ?

Thanks.Sure...

How often do you dump the transaction log?

But I don't think it's advisable...

How big a database are we talking about...

Ever consider compression?|||I often dump my backups across the network to a share on another server. It won't work with very large databases very well, but I've had pretty good luck so far. I find that writing backups to tape can be extremely slow.

As for not keeping the transaction logs, I have to agree with Brett; I would prefer to keep mine.

Regards,

hmscott|||Do you dump across a network, or locally the copy?

I've always thought a dump over a network could corrupt the dump

Never seen it...just always believed it could happen...|||I had all kinds of problems with it in 6.5 and 7.0. I've never seen any problems with it in 2000 though. We do it all the time. All of our servers are dumped to a central repository. We even do restores from there, including log shipping restores. I've never had any corruption doing it this way. Of course, we do have a dual 16gb core with fiber to all servers. We're upgrading to dual 64gb. A lot has changed over the years I guess.

I would definitely consider compression if I were that strapped on space and bandwidth. Many times SQL Backup files will shrink to 70-80 percent of the original size.