Log Shipping NTFS compressed files WAN

If the compression attribute is set on both the source SQL Server directory
and the target SQL Server directory for a log shipping configuration, will
the log files be uncompressed and then recompressed when the copy is made?
Or will the files remain compressed while the copy is taking place? If
WIN2K and SS are smart enough to handle the latter, it will speed up the
transfer of files across a WAN link.This is purely an OS thing, nothing to do with SQL.
See the quote from the following KB article
http://support.microsoft.com/?kbid=251186
When you copy or move a compressed NTFS file to a different folder, NTFS
decompresses the file, copies or moves the file to the new location, and
then recompresses the file. This behavior occurs even when the file is
copied or moved between folders on the same computer. Compressed files are
also expanded before copying over the network, so NTFS compression does not
save network bandwidth
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Don Ferguson" <don@.nospamplease> wrote in message
news:eVy5m1wRDHA.1552@.TK2MSFTNGP10.phx.gbl...
If the compression attribute is set on both the source SQL Server directory
and the target SQL Server directory for a log shipping configuration, will
the log files be uncompressed and then recompressed when the copy is made?
Or will the files remain compressed while the copy is taking place? If
WIN2K and SS are smart enough to handle the latter, it will speed up the
transfer of files across a WAN link.|||Thanks Jasper!
Your response and the KB link answers my question even if this has nothing
to do with SQL Server.
I guess I need to look into SQL LiteSpeed or SQLZIP for a possible solution.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OZtmZexRDHA.2128@.TK2MSFTNGP12.phx.gbl...
> This is purely an OS thing, nothing to do with SQL.
> See the quote from the following KB article
> http://support.microsoft.com/?kbid=251186
> When you copy or move a compressed NTFS file to a different folder, NTFS
> decompresses the file, copies or moves the file to the new location, and
> then recompresses the file. This behavior occurs even when the file is
> copied or moved between folders on the same computer. Compressed files are
> also expanded before copying over the network, so NTFS compression does
not
> save network bandwidth
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Don Ferguson" <don@.nospamplease> wrote in message
> news:eVy5m1wRDHA.1552@.TK2MSFTNGP10.phx.gbl...
> If the compression attribute is set on both the source SQL Server
directory
> and the target SQL Server directory for a log shipping configuration, will
> the log files be uncompressed and then recompressed when the copy is made?
> Or will the files remain compressed while the copy is taking place? If
> WIN2K and SS are smart enough to handle the latter, it will speed up the
> transfer of files across a WAN link.
>
>|||I'm a big fan of SQL Litespeed, does exactly what it says on the tin :-)
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Don Ferguson" <don@.nospamplease> wrote in message
news:evh15xxRDHA.2316@.tk2msftngp13.phx.gbl...
Thanks Jasper!
Your response and the KB link answers my question even if this has nothing
to do with SQL Server.
I guess I need to look into SQL LiteSpeed or SQLZIP for a possible solution.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OZtmZexRDHA.2128@.TK2MSFTNGP12.phx.gbl...
> This is purely an OS thing, nothing to do with SQL.
> See the quote from the following KB article
> http://support.microsoft.com/?kbid=251186
> When you copy or move a compressed NTFS file to a different folder, NTFS
> decompresses the file, copies or moves the file to the new location, and
> then recompresses the file. This behavior occurs even when the file is
> copied or moved between folders on the same computer. Compressed files are
> also expanded before copying over the network, so NTFS compression does
not
> save network bandwidth
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Don Ferguson" <don@.nospamplease> wrote in message
> news:eVy5m1wRDHA.1552@.TK2MSFTNGP10.phx.gbl...
> If the compression attribute is set on both the source SQL Server
directory
> and the target SQL Server directory for a log shipping configuration, will
> the log files be uncompressed and then recompressed when the copy is made?
> Or will the files remain compressed while the copy is taking place? If
> WIN2K and SS are smart enough to handle the latter, it will speed up the
> transfer of files across a WAN link.
>
>

Log Shipping Directory Change

Anyone know how to sucessfully change the location of the transaction
log files and still get Log Shipping to continue to work?
I went in and changed the location of where the transaction logs were
stored. The logs were sucessfully writing to the new directory, but
the copy job on the destination server was not finding them. I assume
it was still looking in the old directory, because the job was
executing successfully - it just wasn't doing anything.
I think it has to do with the setting 'Network share name for backup
directory.' You set that during set-up of log shipping, but I don't
see anywhere to edit that later on. I even tried dropping and
readding the destination server - to no avail.
Any ideas?The LogShipping Copy and Restore Jobs on the destination server are still
pointing to the old location. Thesse are jobs are created automatically
during the logshipping setup process and you can't change it. I will advice
that you remove the logshipping and created it again.
Egbon.
"Jeff Albenberg" <jalbenberg@.yahoo.com> wrote in message
news:e9dc0a21.0307290931.68bb5d1c@.posting.google.com...
> Anyone know how to sucessfully change the location of the transaction
> log files and still get Log Shipping to continue to work?
> I went in and changed the location of where the transaction logs were
> stored. The logs were sucessfully writing to the new directory, but
> the copy job on the destination server was not finding them. I assume
> it was still looking in the old directory, because the job was
> executing successfully - it just wasn't doing anything.
> I think it has to do with the setting 'Network share name for backup
> directory.' You set that during set-up of log shipping, but I don't
> see anywhere to edit that later on. I even tried dropping and
> readding the destination server - to no avail.
> Any ideas?

Log Shipping - log shipping transaction log destination directory

I am trying to set up log shipping between two servers. Secondary server is
going to be a stand-by and light reporting server. My question is 'can I
point log shipping transaction log destination directory to network share
folder?'. Database backup file is pretty big and I'd like to store them on
network. Is it possible?
Thanks in advance,
Jay
yes you can. make sure that you give the accounts running sqlserver and
sqlserveragent read/write permission.
Thanks
Yunwen
"Jay Lee" wrote:

> I am trying to set up log shipping between two servers. Secondary server is
> going to be a stand-by and light reporting server. My question is 'can I
> point log shipping transaction log destination directory to network share
> folder?'. Database backup file is pretty big and I'd like to store them on
> network. Is it possible?
> Thanks in advance,
> Jay