Subject | Re: [firebird-support] Symantec livestate recovery |
---|---|
Author | Ann W. Harrison |
Post date | 2005-03-25T19:14:54Z |
Steffen Heil wrote:
Here's the text from Symantec. As far as I know, Firebird does not
support VSS.
Scenario 4—Database backup
IT administrators can backup both Microsoft® VSS compliant databases
and those that are not VSS compliant. Databases that support VSS will
automatically be synchronized when the volume they reside on is imaged
with Symantec LiveState Recovery. For databases that do not offer VSS
support, administrators can insert commands into the GUI that will run
before the snapshot is captured, after the snapshot is captured, and
after the image has been created. For example, the IT administrator
could use a command file to put an Oracle™ database in backup mode,
take the snapshot (this takes milliseconds), take the Oracle database
out of backup mode, and continue to create the LiveState image file.
This allows creation of a complete system image by either quiescing or
stopping the database briefly.
Regards,
Ann
> HiI think you need to quiesce the database to get the view.
>>
>>No problem as long as you follow the instructions and quiesce
>>the database.
>
>
> But why?
> The database file the copy programm sees is frozen. The firebird server's
> writes don't hit that view...
>
Here's the text from Symantec. As far as I know, Firebird does not
support VSS.
Scenario 4—Database backup
IT administrators can backup both Microsoft® VSS compliant databases
and those that are not VSS compliant. Databases that support VSS will
automatically be synchronized when the volume they reside on is imaged
with Symantec LiveState Recovery. For databases that do not offer VSS
support, administrators can insert commands into the GUI that will run
before the snapshot is captured, after the snapshot is captured, and
after the image has been created. For example, the IT administrator
could use a command file to put an Oracle™ database in backup mode,
take the snapshot (this takes milliseconds), take the Oracle database
out of backup mode, and continue to create the LiveState image file.
This allows creation of a complete system image by either quiescing or
stopping the database briefly.
Regards,
Ann