April 1, 2009 at 5:59 am
Hi,
I am very new to Lightspeed. I need to backup a database having the size of around 400 GB. I don't have enough space in single drive to accommodate the entire backup file. So planning to split up the backup file into multiple files and store in different drives using Lightspeed.
Please clarify me , Can Litespeed split a backup into several different files?
Regards,
Pramila
April 1, 2009 at 6:12 am
Hi Pramila,
Why dont you go for a filegroup backup. I think litespeed doesn't support splitting of backup's. Check out the help file of litespeed. It contains some examples on how to take backup using litespeed. Litespeed is much better than normal backup because it reduces the size of backup file. I have seen a 130gb backup file taken by sqlserver getting reduced to 40gb when taken by litespeed. Try it once and checkout.
Thanks
Chandra Mohan N
[font="Verdana"]Thanks
Chandra Mohan[/font]
April 1, 2009 at 9:10 pm
Thanks a lot for your valuable sugessions :-):-):-)
April 1, 2009 at 9:14 pm
Litespeed definitely does support splitting a backup over multiple files: we use it that way for several of our large production databases. Just specify multiple ",@file = '...'" clauses and the backup will be split approximately evenly across the files.
April 1, 2009 at 9:42 pm
Keep in mind that you need all these files for a restore. It's not like you get partial data with some files. If you don't have them all, you lose all data.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
April 2, 2009 at 6:59 am
At my old place I once did a test with Litespeed on a c 300 GB DB. I don't have the exact figures, but when backing up to 1 file to took about 13 hours to complete, using basic compression and 128-bit encryption. When backing up to 4 files (one file per CPU core) it took under 90 minutes to complete.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 2, 2009 at 9:20 am
We are currently using LiteSpeed as well - we are getting about 70% reduction in file size and using 128 bit RC4 encryption. A backup of a database consisting of .625 Tb data and .125 Tb transaction log takes just about 55 minutes to a single file ! Oh, the backup file is 180 Gb.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
April 3, 2009 at 2:24 am
I think my results and rudy's results show that backup performance is affected by how your server is configured. You probably need to try various options and find the simplest way to get the backup done in the time you want to allow for it.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 3, 2009 at 7:35 am
Just to add to Ed's comments - we did benchmarking of all of the encryption options available and found no noticable difference in execution time, backup size or CPU utilization. As for the other options we use LiteSpeed defaults, lest the encryption, right out of the box !
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
April 3, 2009 at 8:10 am
Some tests done where I work now show about a 5% penalty time and CPU penality in using Litespeed encryption, but backup size is has less than 1% difference, compared to not using encryption. The amount you save by compression varies according to your data, but normally a Litespeed backup saves between 60% and 75% of disk space compared to SQL Server native backup.
Some tests done recently at my old place showed that SQL Server 2008 native backup with compression took a bit less disk space than Litespeed compression level 1 (the Litespeed default) but slightly more CPU and elapsed time. It looked like Litespeed compression level 2 is roughly equivalent to SQL Server 2008 backup compresion.
However if you add encryption to SQL Server backup compression you get a backup much the same size as without compression that takes much the same CPU and elapsed time to create as a non-compressed backup. This gives a big advantage to Litespeed where encryption has virtually no penalty.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 3, 2009 at 8:25 am
Good information to know about 2008 Ed - we are bypassing it for now - maybe by 2010 MS will get it fixed ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
June 3, 2009 at 3:08 pm
Hello,
In case third party tool, LightSpeed is not an option, following basic backup script can be used:
backup database DB1 to
disk= 'DiskA:\DataFolder\DataFile01.bak',
disk= 'DiskB:\DataFolder\Data'File02.bak,
disk= 'DiskC:\DataFolder\DataFile03.bak' with init
Ex. if DB1 is 60GB, it will result in 3 backup files, each of app. size of 20GB. This will speed up the backup, if the disks are physically separate.
December 21, 2010 at 3:42 am
Dear Chandra Garu
Using LiteSpeed utility, we can take Splitted backup of Database. Let's think, I have a database of size 500 Gb and none of the drive has free space of 500 GB, in that case, we can get a splitted backup of the database into 2/3 drives with split. the tool will evenly distribute the load.
But, I am not sure whether this works for backup backup method!
If you're aware, please share the process!!
Thanks.
December 21, 2010 at 3:43 am
Dear Chandra Garu
Using LiteSpeed utility, we can take Splitted backup of Database. Let's think, I have a database of size 500 Gb and none of the drive has free space of 500 GB, in that case, we can get a splitted backup of the database into 2/3 drives with split. the tool will evenly distribute the load.
But, I am not sure whether this works for backup backup method!
If you're aware, please share the process!!
Thanks.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply