|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
logshipping on 2000
we used logshipping between primary servers and secondary server, the
distance is more than 1000 miles, the copy job need to copy a 60G files each week, is there anyway to fast the process? thanks Hi
Can you explain how did you set up Log Shipping? > week, is there anyway to fast the process? thanks FTP? I have not tested ,sorryShow quoteHide quote "tulip" <tu***@discussions.microsoft.com> wrote in message news:36E0F184-C85F-457A-86AC-436988C2391B@microsoft.com... > we used logshipping between primary servers and secondary server, the > distance is more than 1000 miles, the copy job need to copy a 60G files > each > week, is there anyway to fast the process? thanks Set up the copy job and load job on the secondary server.
Show quoteHide quote "Uri Dimant" wrote: > Hi > Can you explain how did you set up Log Shipping? > > > week, is there anyway to fast the process? thanks > > FTP? I have not tested ,sorry > > > > "tulip" <tu***@discussions.microsoft.com> wrote in message > news:36E0F184-C85F-457A-86AC-436988C2391B@microsoft.com... > > we used logshipping between primary servers and secondary server, the > > distance is more than 1000 miles, the copy job need to copy a 60G files > > each > > week, is there anyway to fast the process? thanks > > > tulip
You mean two jobs (FULL backup and LOG backups)? Show quoteHide quote "tulip" <tu***@discussions.microsoft.com> wrote in message news:493F2B6F-83DB-4426-919F-56DBF3D75EA7@microsoft.com... > Set up the copy job and load job on the secondary server. > > "Uri Dimant" wrote: > >> Hi >> Can you explain how did you set up Log Shipping? >> >> > week, is there anyway to fast the process? thanks >> >> FTP? I have not tested ,sorry >> >> >> >> "tulip" <tu***@discussions.microsoft.com> wrote in message >> news:36E0F184-C85F-457A-86AC-436988C2391B@microsoft.com... >> > we used logshipping between primary servers and secondary server, the >> > distance is more than 1000 miles, the copy job need to copy a 60G files >> > each >> > week, is there anyway to fast the process? thanks >> >> >> Consider using Red Gate's SQL Backup. They have log shipping built in and
they compress the backup files on the fly: http://www.red-gate.com/products/sql_backup/index_2.htm -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "tulip" <tu***@discussions.microsoft.com> wrote in message we used logshipping between primary servers and secondary server, thenews:36E0F184-C85F-457A-86AC-436988C2391B@microsoft.com... distance is more than 1000 miles, the copy job need to copy a 60G files each week, is there anyway to fast the process? thanks Distance is irrelavant. You need to find out the throughput of your link
(i.e. how many MBs can it push through per second?), and determine if you have enough time for copying 60GB. Linchi Show quoteHide quote "tulip" wrote: > we used logshipping between primary servers and secondary server, the > distance is more than 1000 miles, the copy job need to copy a 60G files each > week, is there anyway to fast the process? thanks it is 300M link. currently took us 30+hours to copy over. Each hour push
about 2G. I think the copy mechnism used by sql job is not efficient? Show quoteHide quote "Linchi Shea" wrote: > Distance is irrelavant. You need to find out the throughput of your link > (i.e. how many MBs can it push through per second?), and determine if you > have enough time for copying 60GB. > > Linchi > > "tulip" wrote: > > > we used logshipping between primary servers and secondary server, the > > distance is more than 1000 miles, the copy job need to copy a 60G files each > > week, is there anyway to fast the process? thanks Have you looked at Red Gate's SQL Backup? We're getting up to 80%
compression. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "tulip" <tu***@discussions.microsoft.com> wrote in message it is 300M link. currently took us 30+hours to copy over. Each hour pushnews:86E9D250-95AB-4D5B-BB18-8F5946FC8A50@microsoft.com... about 2G. I think the copy mechnism used by sql job is not efficient? Show quoteHide quote "Linchi Shea" wrote: > Distance is irrelavant. You need to find out the throughput of your link > (i.e. how many MBs can it push through per second?), and determine if you > have enough time for copying 60GB. > > Linchi > > "tulip" wrote: > > > we used logshipping between primary servers and secondary server, the > > distance is more than 1000 miles, the copy job need to copy a 60G files > > each > > week, is there anyway to fast the process? thanks compression on t-log?
Show quoteHide quote "Tom Moreau" wrote: > Have you looked at Red Gate's SQL Backup? We're getting up to 80% > compression. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "tulip" <tu***@discussions.microsoft.com> wrote in message > news:86E9D250-95AB-4D5B-BB18-8F5946FC8A50@microsoft.com... > it is 300M link. currently took us 30+hours to copy over. Each hour push > about 2G. I think the copy mechnism used by sql job is not efficient? > > "Linchi Shea" wrote: > > > Distance is irrelavant. You need to find out the throughput of your link > > (i.e. how many MBs can it push through per second?), and determine if you > > have enough time for copying 60GB. > > > > Linchi > > > > "tulip" wrote: > > > > > we used logshipping between primary servers and secondary server, the > > > distance is more than 1000 miles, the copy job need to copy a 60G files > > > each > > > week, is there anyway to fast the process? thanks > > Compression on all backups. When you log ship, you backup the transaction
log, copy it to the backup server and then restore it. By compressing the log, you consume less disk space, but you also have less to shove through the network. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "tulip" <tu***@discussions.microsoft.com> wrote in message compression on t-log?news:F42CDDAC-89B3-4A4B-83A5-595AE074EEF3@microsoft.com... Show quoteHide quote "Tom Moreau" wrote: > Have you looked at Red Gate's SQL Backup? We're getting up to 80% > compression. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "tulip" <tu***@discussions.microsoft.com> wrote in message > news:86E9D250-95AB-4D5B-BB18-8F5946FC8A50@microsoft.com... > it is 300M link. currently took us 30+hours to copy over. Each hour push > about 2G. I think the copy mechnism used by sql job is not efficient? > > "Linchi Shea" wrote: > > > Distance is irrelavant. You need to find out the throughput of your link > > (i.e. how many MBs can it push through per second?), and determine if > > you > > have enough time for copying 60GB. > > > > Linchi > > > > "tulip" wrote: > > > > > we used logshipping between primary servers and secondary server, the > > > distance is more than 1000 miles, the copy job need to copy a 60G > > > files > > > each > > > week, is there anyway to fast the process? thanks > > Hi Tom,
i set up the log shipping on red gate, but didn't stop the one on the original server (still back up t-log using sql server job agent) for a test. So i have same database log ship to different db servers, one use sql server , one use sql backup. Backup and restore complete successfully, and the backup and copy jobs all created using sql backup. But the restore t-log job failed with sql backup tool, with error 6/22/2009 3:55:00 PM: Warning 170: Log files are not in sequence: 'LOG_xxx_20090622153005.sqb' and 'LOG_xxx_20090622154504.sqb' 6/22/2009 3:55:00 PM: Restoring xxx (transaction logs) from: 6/22/2009 3:55:00 PM: \\xxx\LOG_xxx_20090622153005.sqb 6/22/2009 3:55:00 PM: RESTORE LOG [xxx] FROM VIRTUAL_DEVICE = 'SQLBACKUP_C6FB8633-3251-457E-AD73-B0B60B907805' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , NORECOVERY 6/22/2009 3:55:00 PM: SQL Server error SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally. SQL error 4305: SQL error 4305: The log in this backup set begins at LSN 829688000000280700001, which is too late to apply to the database. An earlier log backup that includes LSN 829683000002276400001 can be restored. the network share i use in the set up is on the dest server where i want the t-log shipped to. The backup started on 1:50pm, the first t-log backup is 3:00pm. could you share with me your experience? many thanks Show quoteHide quote "Tom Moreau" wrote: > Compression on all backups. When you log ship, you backup the transaction > log, copy it to the backup server and then restore it. By compressing the > log, you consume less disk space, but you also have less to shove through > the network. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "tulip" <tu***@discussions.microsoft.com> wrote in message > news:F42CDDAC-89B3-4A4B-83A5-595AE074EEF3@microsoft.com... > compression on t-log? > > "Tom Moreau" wrote: > > > Have you looked at Red Gate's SQL Backup? We're getting up to 80% > > compression. > > > > -- > > Tom > > > > ---------------------------------------------------- > > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > > SQL Server MVP > > Toronto, ON Canada > > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > > > > "tulip" <tu***@discussions.microsoft.com> wrote in message > > news:86E9D250-95AB-4D5B-BB18-8F5946FC8A50@microsoft.com... > > it is 300M link. currently took us 30+hours to copy over. Each hour push > > about 2G. I think the copy mechnism used by sql job is not efficient? > > > > "Linchi Shea" wrote: > > > > > Distance is irrelavant. You need to find out the throughput of your link > > > (i.e. how many MBs can it push through per second?), and determine if > > > you > > > have enough time for copying 60GB. > > > > > > Linchi > > > > > > "tulip" wrote: > > > > > > > we used logshipping between primary servers and secondary server, the > > > > distance is more than 1000 miles, the copy job need to copy a 60G > > > > files > > > > each > > > > week, is there anyway to fast the process? thanks > > > > > > No surprise there. All transaction log backups must be restored in the
exact same order in which they were backed up - regardless of whether you used a native backup or a SQL Server backup. The easiest thing to do here is pick which one you want to use and use it exclusively. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "tulip" <tu***@discussions.microsoft.com> wrote in message i set up the log shipping on red gate, but didn't stop the one on thenews:E3A76C30-6833-4300-9432-B1A8DCC8A04D@microsoft.com... Hi Tom, original server (still back up t-log using sql server job agent) for a test. So i have same database log ship to different db servers, one use sql server , one use sql backup. Backup and restore complete successfully, and the backup and copy jobs all created using sql backup. But the restore t-log job failed with sql backup tool, with error 6/22/2009 3:55:00 PM: Warning 170: Log files are not in sequence: 'LOG_xxx_20090622153005.sqb' and 'LOG_xxx_20090622154504.sqb' 6/22/2009 3:55:00 PM: Restoring xxx (transaction logs) from: 6/22/2009 3:55:00 PM: \\xxx\LOG_xxx_20090622153005.sqb 6/22/2009 3:55:00 PM: RESTORE LOG [xxx] FROM VIRTUAL_DEVICE = 'SQLBACKUP_C6FB8633-3251-457E-AD73-B0B60B907805' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , NORECOVERY 6/22/2009 3:55:00 PM: SQL Server error SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally. SQL error 4305: SQL error 4305: The log in this backup set begins at LSN 829688000000280700001, which is too late to apply to the database. An earlier log backup that includes LSN 829683000002276400001 can be restored. the network share i use in the set up is on the dest server where i want the t-log shipped to. The backup started on 1:50pm, the first t-log backup is 3:00pm. could you share with me your experience? many thanks Show quoteHide quote "Tom Moreau" wrote: > Compression on all backups. When you log ship, you backup the transaction > log, copy it to the backup server and then restore it. By compressing the > log, you consume less disk space, but you also have less to shove through > the network. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "tulip" <tu***@discussions.microsoft.com> wrote in message > news:F42CDDAC-89B3-4A4B-83A5-595AE074EEF3@microsoft.com... > compression on t-log? > > "Tom Moreau" wrote: > > > Have you looked at Red Gate's SQL Backup? We're getting up to 80% > > compression. > > > > -- > > Tom > > > > ---------------------------------------------------- > > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > > SQL Server MVP > > Toronto, ON Canada > > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > > > > "tulip" <tu***@discussions.microsoft.com> wrote in message > > news:86E9D250-95AB-4D5B-BB18-8F5946FC8A50@microsoft.com... > > it is 300M link. currently took us 30+hours to copy over. Each hour push > > about 2G. I think the copy mechnism used by sql job is not efficient? > > > > "Linchi Shea" wrote: > > > > > Distance is irrelavant. You need to find out the throughput of your > > > link > > > (i.e. how many MBs can it push through per second?), and determine if > > > you > > > have enough time for copying 60GB. > > > > > > Linchi > > > > > > "tulip" wrote: > > > > > > > we used logshipping between primary servers and secondary server, > > > > the > > > > distance is more than 1000 miles, the copy job need to copy a 60G > > > > files > > > > each > > > > week, is there anyway to fast the process? thanks > > > > > >  
Other interesting topics
Run 32-bit and 64-bit instances on same machine
Reseeding identity field Change Column Position SQL Server 2008 / 2005 / 2000 / 7 / 6.5 largest possible database? error logging on SQL 2008 Schedule windows server and sql server reboot weekly Conversion from nvarchar to varchar Tempdb log SQL Help Compare Table Structure |
|||||||||||||||||||||||
