🚀 go-pugleaf

Xavier,

Certainly an offline backup can be restored ... well, not restored in the
usual sense of the word, perhaps, but the operating system files can be
copied over the production files. Keep in mind, however, that this technique
does not capture any transactions entered since the time of the backup ...
thus it can not be used to support either a strategy that requires recovery
to the point of failure, or even a recovery to a point in time.

If this is your sole backup/recovery strategy then consider setting the
transaction log to truncation at checkpoint, because the transaction log is
going to be useless.

The DUMP and LOAD commands built within SQL Server 6.5 can support both
recovery to the point of failure, and a recovery to a point in time, so they
are both more powerful and more generic.

----------------------------------------------------------
BP Margolin
Please reply only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
can be cut and pasted into Query Analyzer is appreciated.

"Xavier S. Lescalier" <xlescalier@euromold.alcatelDOTcom> wrote in message
news:96thlo$bhm$1@bt02e2.god.bel.alcatel.be...
> Hi,
>
> I stop every night my SQL Server (6.5) service via a "net stop" command
> before the backup software runs.
>
> I've heard that an offline backup is unusable in case you need to restore
> your database. Is that true ?
>
> I know that buying a backup agent would be a better solution, but is an
> offline backup really so bad ?
>
> Regards,
>
>
> Xavier Lescalier.
>
>