Home
Forums
New posts
What's new
New posts
Latest activity
Advertise
Resources
Log in
Register
What's new
New posts
Menu
Log in
Register
Install the app
Install
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
Restore of SQL 2K
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="SSAJAROFF92" data-source="post: 21034" data-attributes="member: 2811"><p>Crawford :</p><p></p><p>SQL backup tools are pretty good to backup databases to disk files or tapes,</p><p>and they work </p><p>well even while regular users are working. I use them everyday and haven't</p><p>had any trouble yet.</p><p>All my troubles were due to faulty tape drives or magnetic media.</p><p>If your DBs sum less than 50 Gb, you may keep backing them up with native</p><p>SQL commands such </p><p>as BACKUP DATABASE blabla TO TAPE='\\.\TAPE0' or BACKUP DATABASE blabla TO</p><p>DISK='C:\MYFILE.BKP'.</p><p>Typical DLT performance with native SQL tools is around 7 Gb per hour.</p><p>Arcserve, Veritas and Seagate tools provide much better performance;</p><p>nevertheless, you can </p><p>safely backup a 200 Gb with SQL commands, it just will take a loooong time</p><p>(about 30 hours!).</p><p>I've recovered NT/W2K Enterprise & Deployment servers from scratch about</p><p>twenty times, and </p><p>the most important point is to backup all SQL databases using SQL compliant</p><p>tools.</p><p>Don't try to backup SQL databases by shutting services down, copying</p><p>physical MDF and LDF files, </p><p>etc; that's the usual highway to DBA hell.</p><p>If you need further support, feel free to contact me :</p><p></p><p>Sebastian Sajaroff</p><p><a href="mailto:ssajaroff@grupoassa.com">ssajaroff@grupoassa.com</a></p><p>Grupo ASSA, Argentina</p></blockquote><p></p>
[QUOTE="SSAJAROFF92, post: 21034, member: 2811"] Crawford : SQL backup tools are pretty good to backup databases to disk files or tapes, and they work well even while regular users are working. I use them everyday and haven't had any trouble yet. All my troubles were due to faulty tape drives or magnetic media. If your DBs sum less than 50 Gb, you may keep backing them up with native SQL commands such as BACKUP DATABASE blabla TO TAPE='\\.\TAPE0' or BACKUP DATABASE blabla TO DISK='C:\MYFILE.BKP'. Typical DLT performance with native SQL tools is around 7 Gb per hour. Arcserve, Veritas and Seagate tools provide much better performance; nevertheless, you can safely backup a 200 Gb with SQL commands, it just will take a loooong time (about 30 hours!). I've recovered NT/W2K Enterprise & Deployment servers from scratch about twenty times, and the most important point is to backup all SQL databases using SQL compliant tools. Don't try to backup SQL databases by shutting services down, copying physical MDF and LDF files, etc; that's the usual highway to DBA hell. If you need further support, feel free to contact me : Sebastian Sajaroff [email]ssajaroff@grupoassa.com[/email] Grupo ASSA, Argentina [/QUOTE]
Verification
Post reply
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
Restore of SQL 2K
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top
