WSS v3 not MOSS. The SQL DBs are being backed up using Symantec BE SQL
Agent, but I have also been backing up all sites individually using stsadm
(we don't have many sites and the sites are not large).

I just read sites should first be locked before backing up using stsadm and
then unlocked after, and about the new getsitelock and setsitelock command
parameters for WSS v3. Which of course I have not been doing, oops.

So, is this what batch file should look like?:

stsadm.exe -o setsitelock -url <url of site> -lock noaccess
stsadm.exe -o backup -url <url of site> -filename <file> -overwrite
stsadm.exe -o setsitelock -url <url of site> -lock none

for each site backed up?

And when/why would I use getsitelock in batch file? Is that for returning
the current lock condition of site? e.g. If getsitelock = none then
setsitelock to noaccess ?

Thanks, not much info on these 2 new commands I could find. Just want to be
sure I am on right track.

jremmc

RE: WSS v3 stsadm lock/unlock sites by v-alxie

v-alxie
Thu May 10 20:59:46 CDT 2007

------=_NextPart_0001_04CE1212
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Jremmc,

I am Alex from Microsoft TechNet Newsgroup.

This is a quick note to inform you that I have received this post and I am
currently researching on this question.

Your patience would be highly appreciated.

Regards,

Alex Xie

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_04CE1212
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hi Jremmc,
\par
\par I am Alex from Microsoft TechNet Newsgroup.
\par
\par This is a quick note to inform you that I have received this post and I am currently researching on this question.
\par
\par Your patience would be highly appreciated.
\par
\par Regards,
\par
\par Alex Xie
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par }
------=_NextPart_0001_04CE1212--


RE: WSS v3 stsadm lock/unlock sites by v-alxie

v-alxie
Fri May 11 06:54:39 CDT 2007

------=_NextPart_0001_06EED6E3
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Jremmc,

Thank you for your patience.

Please be assured that you are following the right method to back the sites
in MOSS 2007.

"stsadm.exe -o setsitelock -url <url of site> -lock noaccess" will set the
site to unavailable to all users.

"stsadm.exe -o backup -url <url of site> -filename <file> -overwrite" will
definitely backup the site.

"stsadm.exe -o setsitelock -url <url of site> -lock none" will set the site
to unlock.

As to the getsitelock, since this is a new parameter in WSS 3.0/MOSS 2007,
I will still continue to help you to find the resource which describes the
function of it via our internal channels.

I will keep you posted.

Regards,

Alex Xie
Microsoft Online Partner Support

======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.

We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
------=_NextPart_0001_06EED6E3
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hi Jremmc,
\par
\par Thank you for your patience.
\par
\par Please be assured that you are following the right method to back the sites in MOSS 2007.
\par
\par "stsadm.exe -o setsitelock -url <url of site> -lock noaccess" will set the site to unavailable to all users.
\par
\par "stsadm.exe -o backup -url <url of site> -filename <file> -overwrite" will definitely backup the site.
\par
\par "stsadm.exe -o setsitelock -url <url of site> -lock none" will set the site to unlock.
\par
\par As to the getsitelock, since this is a new parameter in WSS 3.0/MOSS 2007, I will still continue to help you to find the resource which describes the function of it via our internal channels.
\par
\par I will keep you posted.
\par
\par Regards,
\par
\par Alex Xie
\par Microsoft Online Partner Support
\par
\par ======================================================
\par PLEASE NOTE: The partner managed newsgroups are provided to assist with break/fix issues and simple how to questions.
\par
\par We also love to hear your product feedback!
\par Let us know what you think by posting
\par \tab from the web interface: Partner Feedback
\par \tab from your newsreader: microsoft.private.directaccess.partnerfeedback.
\par We look forward to hearing from you!
\par ======================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue.
\par ======================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par ======================================================
\par }
------=_NextPart_0001_06EED6E3--


RE: WSS v3 stsadm lock/unlock sites by v-alxie

v-alxie
Mon May 14 01:14:09 CDT 2007

------=_NextPart_0001_152A1490
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Jremmc,

This is a quick note to let you know that I have heard from our internal
channel.

"stsadm.exe -o getsitelock" gets a values that specifies whether the site
collection is locked and unavailable for read or write access, "stsadm.exe
-o -setsitelock" sets a value that specifies whether the site collection is
locked and unavailable for read or write access.

Hope it is helpful!

Regards,

Alex Xie

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
X-Tomcat-ID: 197056707
References: <uxsrrS0kHHA.1624@TK2MSFTNGP02.phx.gbl>
<uMgfOA3kHHA.5432@TK2MSFTNGHUB02.phx.gbl>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_0001_06EED6E3"
Content-Transfer-Encoding: 7bit
From: v-alxie@online.microsoft.com (Alex Xie [MSFT])
Organization: Microsoft
Date: Fri, 11 May 2007 11:54:39 GMT
Subject: RE: WSS v3 stsadm lock/unlock sites
X-Tomcat-NG: microsoft.public.sharepoint.windowsservices
Message-ID: <dmHhuM8kHHA.1140@TK2MSFTNGHUB02.phx.gbl>
Newsgroups: microsoft.public.sharepoint.windowsservices
Lines: 90
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.sharepoint.windowsservices:4764
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122

Hi Jremmc,

Thank you for your patience.

Please be assured that you are following the right method to back the sites
in MOSS 2007.

"stsadm.exe -o setsitelock -url <url of site> -lock noaccess" will set the
site to unavailable to all users.

"stsadm.exe -o backup -url <url of site> -filename <file> -overwrite" will
definitely backup the site.

"stsadm.exe -o setsitelock -url <url of site> -lock none" will set the site
to unlock.

As to the getsitelock, since this is a new parameter in WSS 3.0/MOSS 2007,
I will still continue to help you to find the resource which describes the
function of it via our internal channels.

I will keep you posted.

Regards,

Alex Xie
Microsoft Online Partner Support

======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.

We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

------=_NextPart_0001_152A1490
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hi Jremmc,
\par
\par This is a quick note to let you know that I have heard from our internal channel.
\par
\par "stsadm.exe -o getsitelock" gets a values that specifies whether the site collection is locked and unavailable for read or write access, "stsadm.exe -o -setsitelock" sets a value that specifies whether the site collection is locked and unavailable for read or write access.
\par
\par Hope it is helpful!
\par
\par Regards,
\par
\par Alex Xie
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par \pard\li720 --------------------
\par X-Tomcat-ID: 197056707
\par References: <uxsrrS0kHHA.1624@TK2MSFTNGP02.phx.gbl> <uMgfOA3kHHA.5432@TK2MSFTNGHUB02.phx.gbl>
\par MIME-Version: 1.0
\par Content-Type: multipart/alternative; boundary="----=_NextPart_0001_06EED6E3"
\par Content-Transfer-Encoding: 7bit
\par From: v-alxie@online.microsoft.com (Alex Xie [MSFT])
\par Organization: Microsoft
\par Date: Fri, 11 May 2007 11:54:39 GMT
\par Subject: RE: WSS v3 stsadm lock/unlock sites
\par X-Tomcat-NG: microsoft.public.sharepoint.windowsservices
\par Message-ID: <dmHhuM8kHHA.1140@TK2MSFTNGHUB02.phx.gbl>
\par Newsgroups: microsoft.public.sharepoint.windowsservices
\par Lines: 90
\par Path: TK2MSFTNGHUB02.phx.gbl
\par Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sharepoint.windowsservices:4764
\par NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
\par
\par Hi Jremmc,
\par
\par Thank you for your patience.
\par
\par Please be assured that you are following the right method to back the sites in MOSS 2007.
\par
\par "stsadm.exe -o setsitelock -url <url of site> -lock noaccess" will set the site to unavailable to all users.
\par
\par "stsadm.exe -o backup -url <url of site> -filename <file> -overwrite" will definitely backup the site.
\par
\par "stsadm.exe -o setsitelock -url <url of site> -lock none" will set the site to unlock.
\par
\par As to the getsitelock, since this is a new parameter in WSS 3.0/MOSS 2007, I will still continue to help you to find the resource which describes the function of it via our internal channels.
\par
\par I will keep you posted.
\par
\par Regards,
\par
\par Alex Xie
\par Microsoft Online Partner Support
\par
\par ======================================================
\par PLEASE NOTE: The partner managed newsgroups are provided to assist with break/fix issues and simple how to questions.
\par
\par We also love to hear your product feedback!
\par Let us know what you think by posting
\par \tab from the web interface: Partner Feedback
\par \tab from your newsreader: microsoft.private.directaccess.partnerfeedback.
\par We look forward to hearing from you!
\par ======================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue.
\par ======================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par ======================================================
\par \pard
\par
\par }
------=_NextPart_0001_152A1490--


Re: WSS v3 stsadm lock/unlock sites by jremmc

jremmc
Mon May 14 08:33:47 CDT 2007

Hello Alex,

Thank you. Just to clarify my understanding of your response:

I have WSS not MOSS, but the parameters are for either application.

I am currently *not* using setsitelock; you are indicating by verifying my
proposed batch file that I should use it.

jremmc


"Alex Xie [MSFT]" <v-alxie@online.microsoft.com> wrote in message
news:MlZlY8elHHA.4356@TK2MSFTNGHUB02.phx.gbl...
> Hi Jremmc,
>
> This is a quick note to let you know that I have heard from our internal
> channel.
>
> "stsadm.exe -o getsitelock" gets a values that specifies whether the site
> collection is locked and unavailable for read or write access, "stsadm.exe
> -o -setsitelock" sets a value that specifies whether the site collection
> is
> locked and unavailable for read or write access.
>
> Hope it is helpful!
>
> Regards,
>
> Alex Xie
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --------------------
> X-Tomcat-ID: 197056707
> References: <uxsrrS0kHHA.1624@TK2MSFTNGP02.phx.gbl>
> <uMgfOA3kHHA.5432@TK2MSFTNGHUB02.phx.gbl>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_0001_06EED6E3"
> Content-Transfer-Encoding: 7bit
> From: v-alxie@online.microsoft.com (Alex Xie [MSFT])
> Organization: Microsoft
> Date: Fri, 11 May 2007 11:54:39 GMT
> Subject: RE: WSS v3 stsadm lock/unlock sites
> X-Tomcat-NG: microsoft.public.sharepoint.windowsservices
> Message-ID: <dmHhuM8kHHA.1140@TK2MSFTNGHUB02.phx.gbl>
> Newsgroups: microsoft.public.sharepoint.windowsservices
> Lines: 90
> Path: TK2MSFTNGHUB02.phx.gbl
> Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.sharepoint.windowsservices:4764
> NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>
> Hi Jremmc,
>
> Thank you for your patience.
>
> Please be assured that you are following the right method to back the
> sites
> in MOSS 2007.
>
> "stsadm.exe -o setsitelock -url <url of site> -lock noaccess" will set the
> site to unavailable to all users.
>
> "stsadm.exe -o backup -url <url of site> -filename <file> -overwrite" will
> definitely backup the site.
>
> "stsadm.exe -o setsitelock -url <url of site> -lock none" will set the
> site
> to unlock.
>
> As to the getsitelock, since this is a new parameter in WSS 3.0/MOSS 2007,
> I will still continue to help you to find the resource which describes the
> function of it via our internal channels.
>
> I will keep you posted.
>
> Regards,
>
> Alex Xie
> Microsoft Online Partner Support
>
> ======================================================
> PLEASE NOTE: The partner managed newsgroups are provided to assist with
> break/fix issues and simple how to questions.
>
> We also love to hear your product feedback!
> Let us know what you think by posting
> from the web interface: Partner Feedback
> from your newsreader: microsoft.private.directaccess.partnerfeedback.
> We look forward to hearing from you!
> ======================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from this issue.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ======================================================
>



Re: WSS v3 stsadm lock/unlock sites by v-alxie

v-alxie
Tue May 15 04:46:18 CDT 2007

------=_NextPart_0001_1B12A983
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Jremmc,

You are correct. I was indicating that you are on the right track to backup
the sites through the command lines.

@Echo off
stsadm.exe -o setsitelock -url <url of site1> -lock noaccess
stsadm.exe -o backup -url <url of site1> -filename <file> -overwrite
stsadm.exe -o setsitelock -url <url of site1> -lock none

stsadm.exe -o setsitelock -url <url of site2> -lock noaccess
stsadm.exe -o backup -url <url of site2> -filename <file> -overwrite
stsadm.exe -o setsitelock -url <url of site2> -lock none

Re: WSS v3 stsadm lock/unlock sites by v-alxie

v-alxie
Thu May 17 08:43:22 CDT 2007

------=_NextPart_0001_2638658A
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Jremmc,

How is everything going?

Sincerely,
Alex Xie
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_2638658A
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hi Jremmc,
\par
\par How is everything going?
\par
\par Sincerely,
\par Alex Xie
\par Microsoft Online Partner Support
\par
\par Get Secure! - www.microsoft.com/security
\par
\par =====================================================
\par When responding to posts, please "Reply to Group" via
\par your newsreader so that others may learn and benefit
\par from your issue.
\par =====================================================
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par }
------=_NextPart_0001_2638658A--


Re: WSS v3 stsadm lock/unlock sites by jremmc

jremmc
Fri May 18 12:35:24 CDT 2007

Hi Alex,

Looks like working fine. I've been running the batch file each night at 9:30
PM using Scheduled Tasks, a few hours before the Symantec Backup Agent runs
the SQL backup of the entire databases. No errors in any logs (though not
sure errors would be posted to any log). Each site is getting locked, backed
up, then unlocked, and when locked, browser displays not permitted message
when trying to access site (can't recall exact message but that is the
gist).

getsitelock does indeed report on condition (noaccess, none, etc).

Thanks for your help!

jremmc


"Alex Xie [MSFT]" <v-alxie@online.microsoft.com> wrote in message
news:vz14XlImHHA.5432@TK2MSFTNGHUB02.phx.gbl...
> Hi Jremmc,
>
> How is everything going?
>
> Sincerely,
> Alex Xie
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.



Re: WSS v3 stsadm lock/unlock sites by v-alxie

v-alxie
Mon May 21 05:00:56 CDT 2007

------=_NextPart_0001_3A063DF9
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Jremmc,

Appreciate your update and response. I am glad to hear that the backup job
works fine as expected.

If you have any other questions or concerns, please do not hesitate to
contact us. It is always our pleasure to be of assistance.

Sincerely,
Alex Xie
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: "jremmc" <jremmc@news.postalias>
References: <uxsrrS0kHHA.1624@TK2MSFTNGP02.phx.gbl>
<uMgfOA3kHHA.5432@TK2MSFTNGHUB02.phx.gbl>
<dmHhuM8kHHA.1140@TK2MSFTNGHUB02.phx.gbl>
<MlZlY8elHHA.4356@TK2MSFTNGHUB02.phx.gbl>
<ud2#DyilHHA.1388@TK2MSFTNGP05.phx.gbl>
<bjwplXtlHHA.5432@TK2MSFTNGHUB02.phx.gbl>
<vz14XlImHHA.5432@TK2MSFTNGHUB02.phx.gbl>
Subject: Re: WSS v3 stsadm lock/unlock sites
Date: Fri, 18 May 2007 13:35:24 -0400
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-RFC2646: Format=Flowed; Original
Message-ID: <e$OUsLXmHHA.4120@TK2MSFTNGP06.phx.gbl>
Newsgroups: microsoft.public.sharepoint.windowsservices
NNTP-Posting-Host: 63.144.132.78
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.sharepoint.windowsservices:4969
X-Tomcat-NG: microsoft.public.sharepoint.windowsservices

Hi Alex,

Looks like working fine. I've been running the batch file each night at
9:30
PM using Scheduled Tasks, a few hours before the Symantec Backup Agent runs
the SQL backup of the entire databases. No errors in any logs (though not
sure errors would be posted to any log). Each site is getting locked,
backed
up, then unlocked, and when locked, browser displays not permitted message
when trying to access site (can't recall exact message but that is the
gist).

getsitelock does indeed report on condition (noaccess, none, etc).

Thanks for your help!

jremmc


"Alex Xie [MSFT]" <v-alxie@online.microsoft.com> wrote in message
news:vz14XlImHHA.5432@TK2MSFTNGHUB02.phx.gbl...
> Hi Jremmc,
>
> How is everything going?
>
> Sincerely,
> Alex Xie
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.



------=_NextPart_0001_3A063DF9
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hi Jremmc,
\par
\par Appreciate your update and response. I am glad to hear that the backup job works fine as expected.
\par
\par If you have any other questions or concerns, please do not hesitate to contact us. It is always our pleasure to be of assistance.
\par
\par Sincerely,
\par Alex Xie
\par Microsoft Online Partner Support
\par
\par Get Secure! - www.microsoft.com/security
\par
\par =====================================================
\par When responding to posts, please "Reply to Group" via
\par your newsreader so that others may learn and benefit
\par from your issue.
\par =====================================================
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par \pard\li720 --------------------
\par From: "jremmc" <jremmc@news.postalias>
\par References: <uxsrrS0kHHA.1624@TK2MSFTNGP02.phx.gbl> <uMgfOA3kHHA.5432@TK2MSFTNGHUB02.phx.gbl> <dmHhuM8kHHA.1140@TK2MSFTNGHUB02.phx.gbl> <MlZlY8elHHA.4356@TK2MSFTNGHUB02.phx.gbl> <ud2#DyilHHA.1388@TK2MSFTNGP05.phx.gbl> <bjwplXtlHHA.5432@TK2MSFTNGHUB02.phx.gbl> <vz14XlImHHA.5432@TK2MSFTNGHUB02.phx.gbl>
\par Subject: Re: WSS v3 stsadm lock/unlock sites
\par Date: Fri, 18 May 2007 13:35:24 -0400
\par Lines: 39
\par X-Priority: 3
\par X-MSMail-Priority: Normal
\par X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
\par X-RFC2646: Format=Flowed; Original
\par Message-ID: <e$OUsLXmHHA.4120@TK2MSFTNGP06.phx.gbl>
\par Newsgroups: microsoft.public.sharepoint.windowsservices
\par NNTP-Posting-Host: 63.144.132.78
\par Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
\par Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sharepoint.windowsservices:4969
\par X-Tomcat-NG: microsoft.public.sharepoint.windowsservices
\par
\par Hi Alex,
\par
\par Looks like working fine. I've been running the batch file each night at 9:30
\par PM using Scheduled Tasks, a few hours before the Symantec Backup Agent runs
\par the SQL backup of the entire databases. No errors in any logs (though not
\par sure errors would be posted to any log). Each site is getting locked, backed
\par up, then unlocked, and when locked, browser displays not permitted message
\par when trying to access site (can't recall exact message but that is the
\par gist).
\par
\par getsitelock does indeed report on condition (noaccess, none, etc).
\par
\par Thanks for your help!
\par
\par jremmc
\par
\par
\par "Alex Xie [MSFT]" <v-alxie@online.microsoft.com> wrote in message
\par news:vz14XlImHHA.5432@TK2MSFTNGHUB02.phx.gbl...
\par > Hi Jremmc,
\par >
\par > How is everything going?
\par >
\par > Sincerely,
\par > Alex Xie
\par > Microsoft Online Partner Support
\par >
\par > Get Secure! - www.microsoft.com/security
\par >
\par > =====================================================
\par > When responding to posts, please "Reply to Group" via
\par > your newsreader so that others may learn and benefit
\par > from your issue.
\par > =====================================================
\par >
\par > This posting is provided "AS IS" with no warranties, and confers no
\par > rights.
\par
\par
\par \pard
\par
\par }
------=_NextPart_0001_3A063DF9--