Use dbname; Backup logs with truncate_only;
Go; Quit; In osql or whatever they are calling it these days. Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Robert Cato [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2008 8:22 AM To: NT System Admin Issues Subject: Re: Sharepoint / MOSS woes Stsadm does not flush the logs. I have downloaded the SQL Express management tools, but I still need to research how to use them. Robert On Mon, Aug 18, 2008 at 7:18 AM, Michael B. Smith <[EMAIL PROTECTED]> wrote: Stsadm –o backup DOES include a sql backup. Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com <http://theessentialexchange.com/> From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Monday, August 18, 2008 5:42 AM To: NT System Admin Issues Subject: Sharepoint / MOSS woes Can I start by just saying ARRRRGHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH! Thanks We decided to upgrade our WSS 3 box to MOSS2007 on Thursday. We went through all the docs before hand, got a copy of the backups (we run full backups nightly using STSADM and also get backup of the AAM and the Metabase). As is the way, the install went badly. After 24 hours of us trying to coax the configuration tool to tell us what useraccount it was referring to when it said "invalid user account" we called PSS. That's when the fun really started. We've been assigned a PSS member who's English is poor and their accent is so strong that we've given up asking them to repeat themselves and have just asked them email everything to us, which means things are taking ages. The configuration tool failed to complete at all, even with PSS talking to it, so we started down the route of uninstalling MOSS/WSS and then starting again. Guess what?...you can't uninstall MOSS/WSS unless the configuration tool has completed successfully!! Which is nice, and the 'official' manual uninstall guidelines from MS require that you remove it from add/remove, which you can't. So, after stepping in to the dark, this time with a chap who can speak English and was happy to sit and chat, we've manually removed MOSS and are starting again. And this is really where my question comes in. When using WSS3 in standalone mode (ie just one box running WSS without SQL server installed), does the "STSADM –o backup ..." command constitute a full backup? We thought it did, and have checked the docs which also imply it does. However the PSS chap (now back the non-english speaker) seems to think that we would also need an SQL backup. This in itself is odd, as the standalone install of WSS3 appears to use Windows Internal Database (ie SQL Server 2005 compact or embedded). This doesn't have any management tools with it, and there's no clear indication that it's meant to be managed outside of the app thats written to use it. I'm losing the will to live, and am apparently paying good money for someone to email me links and to confuse us even more than we are able to do ourselves. Rant over :S Olly ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
