Hi Folks,
I haven't worked at multiple SQL Shops so question for those who have;
SQL Backups, which is the perfered way using SQL Server to do the backups or
to use a 3rd backup agent like Backup Execs SQL Agent to do backups?
Right now we use SQL Server to do daily backup to .BAK file; which later
server ops write to tape. And continously we keep running into space
issues; so it was suggested we use Backup Execs SQL Agent to do backups
directly to tape. But I have never used Backup Exec so I couldn't really
say which is better. I know SQL Server has ability to write directly to
tapes, again not something I have used.
Please any insight. Thanks!
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 20053rd party backup softwares has compression feature mostly. So, that may help
you about the storage issues. Check out trial versions of those softwares
and perform your tests. However, compressing databases will be available
with SQL Server 2008.
One tip regarding to taking backups to Tapes... Tapes should be connected to
your SQL Server server directly, you can not take backup to tape when the
tape is on another server.
Taking once full backup daily is not appropriate for most data critical
production servers. First you need to find out what's the tolarable losing
of data for that company. If they say "we do not have any tolerance to lose
any data" (which is quite normal) then you'll use Transaction Log backups
too. So keep the count of Transaction Log backups minimum, you'll need to
use Differential Backups as well. However, you know, it depends...
--
Ekrem Ã?nsoy
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:9ED52060-6CAA-423C-B800-D0CECF8838CE@.microsoft.com...
> Hi Folks,
> I haven't worked at multiple SQL Shops so question for those who have;
> SQL Backups, which is the perfered way using SQL Server to do the backups
> or
> to use a 3rd backup agent like Backup Execs SQL Agent to do backups?
> Right now we use SQL Server to do daily backup to .BAK file; which later
> server ops write to tape. And continously we keep running into space
> issues; so it was suggested we use Backup Execs SQL Agent to do backups
> directly to tape. But I have never used Backup Exec so I couldn't really
> say which is better. I know SQL Server has ability to write directly to
> tapes, again not something I have used.
> Please any insight. Thanks!
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005|||Thanks Ekrem.
In your opinion which one is better, using backup to disk? Or directly to
tape; considering I can get tape drive hooked directly to SQL Server.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005|||It depends on the scenarios. You can see some scenarios from the following
articles.
Some of them:
http://www.smallbusinesscomputing.com/testdrive/article.php/3528326
http://www.storagesearch.com/engenio-art2.html
--
Ekrem Ã?nsoy
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:79E1C65C-5732-4957-B18B-14B765A9D558@.microsoft.com...
> Thanks Ekrem.
> In your opinion which one is better, using backup to disk? Or directly to
> tape; considering I can get tape drive hooked directly to SQL Server.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005|||Thanks! Those are good links, now I can backup some of what I say to
management ;-). Thanks again.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005|||I'm glad they helped, good luck! =)
--
Ekrem Ã?nsoy
"Mohit K. Gupta" <mohitkgupta@.msn.com> wrote in message
news:59BFA06B-DCAE-4840-8CBF-2C36A946D056@.microsoft.com...
> Thanks! Those are good links, now I can backup some of what I say to
> management ;-). Thanks again.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
Showing posts with label folks. Show all posts
Showing posts with label folks. Show all posts
Thursday, March 29, 2012
Wednesday, March 7, 2012
Backup on Local Disk Failing! urgent help plz!
Folks, this is the error i get when backing up user db to local disk:
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
If i copy a file (2gb) to local disk from network it works. The disk have much space. Any ideas;;; :confused:
I get the same error when backuping up even MSDB to a network path using UNC [\\].How large is the db you're trying to back up. How much disk space do you have? Can you backup a very small database?|||As i mentioned; i get the error even backing up MSDB(system) db either on network or local disk. Strangely; when i try backing up any db to local disk using EM; i get the message; backup successfully completed. and the file disappears(0 kb during backup) disappears on the disk!
Killing me!|||How is your SQL Server registered? Are you using the server name or are you using (local) or . ?
Whenever you use the 2 last options to register your server in EM it uses the shared memory driver, If you use the name of your server/instance, It should make it use the network librbary instead. I say that only to get to the point that if it is not a diskspace issue, it may be a memory issue, perhaps RAM going out.
I know that's not really a solution, but perhaps it can help you troubleshoot.|||How is the SQLServerAgent service and the MSSQLServer Service configured on the Log On tab in services? Are they configured to log on as "Local System"? Also, are there any messages in the SQL Server errorlog, or the NT Application event log?|||I don't quite understand "disappears from the disk" part. But in your first post you mentioned something about copying the file (2GB) from a share to a local drive and the backup would work. This leads me to believe that you're appending to the same backup file. I've seen cases when an interupted backup/restore would corrupt the device and no further appends are possible. The only solution would be to re-create the backup file by deleting the old one and creating a new one by backing up your database. Appending is a bad idea because it leads to what I've just described, in which case you DR is down the drain.|||Hi folks, thanx so much for ur input.
RESTARTING the instance just squared it away; so i suspect as mentioned by the fellow, memory problem (but what's the permanent fix?)
I didn't change any SQL-AGENT of SQL changes so far nor did this production machine had been restarted for last 2 months. I just saw my scheduled backup job failed last night and since then i tried restarting the job; backing the databases manually using QA or EM. So i didn't change any settings so far. I couldn't restart the instance during working times so i posted for the suggestion. After the restart it's working.
And, guru? believe me the file on the disk was of zero kb while backing up the db, then after the success message on EM i coldn't find the file; while in QA i get the GENERAL NETWORK error. Wasn't using the append db option!
Howdy!|||See this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452|||Hmmm, and I had this in my Favorites for while it was still in the Premier section...Good catch, pshisbey!|||Many thanx to ya all!
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
If i copy a file (2gb) to local disk from network it works. The disk have much space. Any ideas;;; :confused:
I get the same error when backuping up even MSDB to a network path using UNC [\\].How large is the db you're trying to back up. How much disk space do you have? Can you backup a very small database?|||As i mentioned; i get the error even backing up MSDB(system) db either on network or local disk. Strangely; when i try backing up any db to local disk using EM; i get the message; backup successfully completed. and the file disappears(0 kb during backup) disappears on the disk!
Killing me!|||How is your SQL Server registered? Are you using the server name or are you using (local) or . ?
Whenever you use the 2 last options to register your server in EM it uses the shared memory driver, If you use the name of your server/instance, It should make it use the network librbary instead. I say that only to get to the point that if it is not a diskspace issue, it may be a memory issue, perhaps RAM going out.
I know that's not really a solution, but perhaps it can help you troubleshoot.|||How is the SQLServerAgent service and the MSSQLServer Service configured on the Log On tab in services? Are they configured to log on as "Local System"? Also, are there any messages in the SQL Server errorlog, or the NT Application event log?|||I don't quite understand "disappears from the disk" part. But in your first post you mentioned something about copying the file (2GB) from a share to a local drive and the backup would work. This leads me to believe that you're appending to the same backup file. I've seen cases when an interupted backup/restore would corrupt the device and no further appends are possible. The only solution would be to re-create the backup file by deleting the old one and creating a new one by backing up your database. Appending is a bad idea because it leads to what I've just described, in which case you DR is down the drain.|||Hi folks, thanx so much for ur input.
RESTARTING the instance just squared it away; so i suspect as mentioned by the fellow, memory problem (but what's the permanent fix?)
I didn't change any SQL-AGENT of SQL changes so far nor did this production machine had been restarted for last 2 months. I just saw my scheduled backup job failed last night and since then i tried restarting the job; backing the databases manually using QA or EM. So i didn't change any settings so far. I couldn't restart the instance during working times so i posted for the suggestion. After the restart it's working.
And, guru? believe me the file on the disk was of zero kb while backing up the db, then after the success message on EM i coldn't find the file; while in QA i get the GENERAL NETWORK error. Wasn't using the append db option!
Howdy!|||See this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452|||Hmmm, and I had this in my Favorites for while it was still in the Premier section...Good catch, pshisbey!|||Many thanx to ya all!
Subscribe to:
Posts (Atom)