Someone else also asked this off list. I am the night owl and the 3000
guy in the group. We develop on the LAN, and that is reasonably
accessible at night, and neither users nor developers have much reason
to access the 3000 at night; I am hard-pressed to imagine someone
signing on to the 3000 at night. I am considering living with that risk,
so long as all backup jobs check STORE_JCW and STORE_ERROR (thus the
other posting about the system volume set backup being able to determine
if only the right files were not backed up), and we would catch this.

Not setting LIMIT does admittedly leave us theoretically vulnerable to
sign ons during the backup. How else can this be managed? Besides
passwording the accounts, some kind of system wide UDC to provide a
warning message, or just keep them out, comes to mind. SEC / 3K could
limit hours, but since that can change, maintenance would be a pain.

> -----Original Message-----
> From: Brent Flowers [SMTP:[log in to unmask]]
> Sent: Tuesday, September 22, 1998 8:19 PM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] Quiescing before backups
>
> How sure are you that NOBODY will EVER be on-line late at
> night or early in the morning?  Can your system be accessed
> from "the outside" via modem or internet?  Do you have any
> server or listener jobs running, e.g. odbc, web, or ftp
> servers?
>
> Don't underestimate your users' nocturnal proclivities,
> especially if they can access the system from home or a
> hotel room.
>
> --Brent Flowers
>
> PS:  This is my first posting via Outlook (aka Lookout!) 98.
> Please notify me if it shows up as mime or html or anything
> other than plain text.