Re: Backups Best Practices
From: Geoff N.Hiten (SRDBA_at_Careerbuilder.com)
Date: 02/18/04
- Next message: Geoff N.Hiten: "Re: Why BACKUP do not work to NET folder ?"
- Previous message: Uri Dimant: "Re: Does DBCC SHRINKFILE on a data file cause the log to grow?"
- Next in thread: mannie: "Re: Backups Best Practices"
- Reply: mannie: "Re: Backups Best Practices"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Feb 2004 10:12:36 -0500
I also do restores to our analytical systems as ETL sources. I don't know
if my setup is the absolute fastest, but it does meet my needs.
I use SQLLiteSpeed to backup to a UNC share on a remote file server. I have
a dedicated Gigabit LAN just for backups and restores. The UNC shares are
on a RAID-10 Ultra-320 SCSI device. I have TLog backups going to another
file server with a slightly slower disk subsystem. I have found that if
Full and Log backups are on the same system, it can sometimes get 'bound up'
trying to service too many disk requests at once.
The UNC host is also the tape host so tape backups and restores happen
to/from the local file system. Any system that has to do backup or restore
on a regular basis is attached to the Backup network.
I don't bother with index rebuilds after a restore unless the backup was
restored to the production system. I use a home-grown log shipping system
to handle most of the data transfer between systems so I am constantly
testing my full and Tlog backups as part of my normal business practices.
-- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org "Steven Toney" <toneys@ibm.net> wrote in message news:uRgZQ7a9DHA.1948@TK2MSFTNGP12.phx.gbl... > we are getting ready to buy sql lite speed too > > testing the demo for backups is impressive wtih decrease file size and speed > > restores seem to take the same amount of time as with native sql versus the > VDI Sqllitespeed > > is this what other are seeing > > we routinely backup DBs in the 100-250 gig range and restore them on another > server for analytical use > > experimenting with ways for smallest over time window for this > > things like backup to local SAN -- restore to other server across network > > back to UNC path on other server -- restore from local SAN > > Trying to copy such large files are a network in windows is too slow -- it > is faster to just backup in SQL and then restore in SQL or move the file > with a tape library > > We soon may have a disked based backup system to try DX30 from quantum > > comments on getting shortest back and restore windows > > example -- a large DB we have create a 170gig backup file the backup restore > rebuild indexes on this puppy takes 15-20 hours -- we do this once a month > as that is the refresh for new data loads -- new data is about 4-6 gig a > month > > > "Geoff N.Hiten" <SRDBA@Careerbuilder.com> wrote in message > news:%23nQaoqX9DHA.2832@tk2msftngp13.phx.gbl... > > I am with Wayne and Tibor on this one. SQL backups (using SQLLiteSpeed > for > > the really big databases) to a UNC share on another machine. I then have > > daily, weekly and monthly rotations to tape with the monthly tapes removed > > and archived. > > > > > > -- > > Geoff N. Hiten > > Microsoft SQL Server MVP > > Senior Database Administrator > > Careerbuilder.com > > > > I support the Professional Association for SQL Server > > www.sqlpass.org > > > > "Wayne Snyder" <wsnyder@computeredservices.com> wrote in message > > news:%23kaRt6W9DHA.2308@TK2MSFTNGP11.phx.gbl... > > > I agree with Tibor, except that I prefer to backup directly to the > remote > > > file system using a unc name, so I don't to coordinate the file > > > copies...(although the backup itself will run slower and eat network > > > bandwidth.) > > > > > > -- > > > Wayne Snyder, MCDBA, SQL Server MVP > > > Computer Education Services Corporation (CESC), Charlotte, NC > > > www.computeredservices.com > > > (Please respond only to the newsgroups.) > > > > > > I support the Professional Association of SQL Server (PASS) and it's > > > community of SQL Server professionals. > > > www.sqlpass.org > > > > > > > > > "mannie" <anonymous@discussions.microsoft.com> wrote in message > > > news:A03011F7-A2F7-46F9-9E10-40EE2A695832@microsoft.com... > > > > It looks like I have been presented with 2 options for backing up to > > tape. > > > > 1. Use veritas SQL Agent and back up the full every <blank> days and > > logs > > > every <blank> days > > > > 2. Backup using native SQL agent to disk and using veritas to backup > > the > > > BAK files to tape every night. > > > > > > > > Anyone have an opinion on which is best and why? > > > > > > > > > > > >
- Next message: Geoff N.Hiten: "Re: Why BACKUP do not work to NET folder ?"
- Previous message: Uri Dimant: "Re: Does DBCC SHRINKFILE on a data file cause the log to grow?"
- Next in thread: mannie: "Re: Backups Best Practices"
- Reply: mannie: "Re: Backups Best Practices"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
