James Harper wrote, sometime around 29/04/06 06:11:
> Is anyone doing this now? Would there be any value in developing an fd
> module specifically to back up these databases?
I do backups of MS SQL 2000 to files and then gzip them (reduces the
backups to about 10% of their original size). Doing th
> ASCII ... binary ... whatever.
>
> I _thought_ those files were ASCII, but it's not terribly important.
> What _is_ important is that the files represent a consistent view of
> the data in the database that can be backed up by normal file backup
> tools.
Sorry. I was probably being a bit pedant
On Mon, 1 May 2006 11:48:55 +1000
"James Harper" <[EMAIL PROTECTED]> wrote:
> > > Not sure where you're coming from here so my answer may not match
> the
> > > intent of your question.
> >
> > I guess my point was simply that backing up transaction logs is an
> > important part of MSSQL, and gene
> > Not sure where you're coming from here so my answer may not match
the
> > intent of your question.
>
> I guess my point was simply that backing up transaction logs is an
> important part of MSSQL, and generally involves dumping them to ASCII
(?)
> files as well, then doing a second step to get
"James Harper" <[EMAIL PROTECTED]> wrote:
> > > Actually, the really correct way is to have a backup 'agent' (MSSQL
> > > specific fd) that sets up a named pipe and then tells the sql server
> to
> > > back up to that named pipe. The agent reads the data from the pipe
> and
> > > sends it (one way
> > Actually, the really correct way is to have a backup 'agent' (MSSQL
> > specific fd) that sets up a named pipe and then tells the sql server
to
> > back up to that named pipe. The agent reads the data from the pipe
and
> > sends it (one way or another) to the backup media.
>
> I suppose. It w
On 30 Apr 2006 at 10:27, Bill Moran wrote:
> "James Harper" <[EMAIL PROTECTED]> wrote:
>
> > > In the case of MSSQL, you can _never_ safely back up the database
> > files.
> > > (Unless, of course, you shut down the database server).
> >
> > Hmmm... I thought that MSSQL spoke VSS and could give
With SQLServer 2000 or higher running on Windows 2003 server with the
VSS enabled Bacula client you will be able to backup your "hot"
database. This is part of the perks of VSS, so you *can* safely backup
your database with it running. With that being said I would still
schedule some form of DB
"James Harper" <[EMAIL PROTECTED]> wrote:
> > In the case of MSSQL, you can _never_ safely back up the database
> files.
> > (Unless, of course, you shut down the database server).
>
> Hmmm... I thought that MSSQL spoke VSS and could give a coherent copy of
> the underlying files. But I was far f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Moran wrote:
> Like most SQL servers, MSSQL has a function do dump the database to a
> text file. You then back up the text file like any other. This is the
> correct way to do a database backup.
You can also code backup agents for SQL Server,
> In the case of MSSQL, you can _never_ safely back up the database
files.
> (Unless, of course, you shut down the database server).
Hmmm... I thought that MSSQL spoke VSS and could give a coherent copy of
the underlying files. But I was far from positive on that so I stand
corrected.
> Like most
"James Harper" <[EMAIL PROTECTED]> wrote:
> Is anyone doing this now? Would there be any value in developing an fd
> module specifically to back up these databases?
>
> As I understand it, VSS allows a coherent copy of the database file to
> be taken, which will get you out of trouble in the case
12 matches
Mail list logo
