Backup time increased

Question

Backup time increased

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply

Rodrigo Acosta SSC-Insane Points: 21261 More actions · Answer 1

But the number of files to backups depends also of how much processor capacity you have. Because multiple backup files enable sql to backup in parallel. And be ware, because if you have multiply backyp files, and you loose one of them, the entire backup is broken. Plus, is adds more administrative issues

peddi_praveen Mr or Mrs. 500 Points: 550 More actions · Answer 2

hi Antares686 n racosta,

thanks for the info,

regards,

praveen

Praveen Kumar Peddi

Tmp SSCommitted Points: 1938 More actions · Answer 3

I finally used the old fashion way...local backup - compression - transfer. All the proccess spend 75 minutes, against the 380 used in the old method.

Thanks all for the suggestions!

toeho SSC Enthusiast Points: 106 More actions · Answer 4

Try sqlzip. http://www.sqlzip.com

Backup local then copy across the network. Sqlzip will compress the backups on the fly instead of laying the files down and then compressing them. I have a 110gb database that only takes an hour to backup and compresses down to 10gb. The restores are extremely fast as well, 45 min to an hour to complete.

Bill Stevenson

MCSE, MCDBA

Bill Stevenson
MCSE, MCDBA

Vik Nat Hall of Fame Points: 3930 More actions · Answer 5

I think its a good practice to backup to local disk first and then schedule a backup to tape later

Vik Nat Hall of Fame Points: 3930 More actions · Answer 6

I have used SQLLITE Speed and am really impressed with it - don't know if we will get the nod to purchase a licence at this moment, but I think its definately worth it.

One of our larger DB's (28GB in size) normally takes around 1:40 hrs to complete a weekly backup to disk. Using SQLLITE, it took 24 mins and backup file size was around 8GB instead of 26GB.