[#CORE-1232] Wrong behaviour of services manager during backup/restore operations

Firebird Core

Wrong behaviour of services manager during backup/restore operations

Created: 26/Apr/07 08:15 AM Updated: 19/Jun/07 09:31 AM

Component/s:

Engine

Affects Version/s:

1.5.3, 2.0.0, 1.5.4, 2.0.1, 2.1 Alpha 1

Fix Version/s:

2.1 Beta 1

Time Tracking:

Not Specified

Environment:

Hardware/OS independent.

Description

« Hide

When performing isc_action_svc_backup or isc_action_svc_restore, result of operation depends upon order of tags in clumplet, passed to SVC_start, and even backup may performed instead of restore. This may easily cause data loss.

All

Comments

Work Log

Change History

Version Control

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Alexander Peshkov added a comment - 26/Apr/07 10:36 AM

Order of tags in clumplet became much less important. The main restriction left is that to specify bkp/res size one must do it in exact order: filename1 size1 filename2 size2 filename_last. But this limitation looks more or less OK.

Tags for dbname and bkp_file may be used in any order, anyway what is given in dbname will be used for database, and what in bkp_file - for backup file name. Also when nothing of replace/create is given for restore operation, services manager defaults to create. Before this fix it was trying to do backup, which taken together with mixed order of dbname and bkp_file might cause backup file loss.