Information Security (inventory/storage) (console)

Gbak: a command column tool. The command has two shards, one shard and one shard (-B/-C) signature Method gbak <Options>-user <username>-Password <password> <source> <destination> 1. copy gbak-B <source> is the source of the information you want to copy, and <destination> is the destination name of the copy. the extension name is. FBK. only sysdba or metadata administrators can submit jobs. for data records in multiple cases, you only need to specify the name of the first case to register the data records. 2. the stored gbak-C <source> is a previous example, And the <destination> is the name selection option of the resource, that is, the command can be used to include the number of bytes before the period, or contain the number of bytes within the period ). Description Function-B [ackup_database] Copy Replica-Bu [ffers] Set cache size for restored Database Stored-C [reate_database] Memory (required memory) Storage-CO [nvert] Upload External table to internal table s Copy-E [xpand] Create a non-linear replica Replica-Fa [ctor] n Region data of the magnetic belt Replica-G [arbage collect] The deleted resources are not cleared at the same time. Replica-I [nactive] All indexes will be stored as inactive Back-Ig [nore] Do not perform checksum when copying logs. Shard-K [ill] Shadows in a non-creation definition copy Memory-L [imbo] Ignore limbo transactions during initial submission Replica-M [etadata] Only metadata table metadata (schema ). Replica-Mo [de] read_write Store a portable/portable resource) Save-Mo [de] read_only Store a unique resource Back-N [o_validity] Do not save the validity constraints. That is, do not store the data. Incompatible format (only used on the same job platform and Firebird Version) Copying-O [ne_at_a_time] Save a table at a time. You can save the table at different times-ol [d_descriptions] Shard format Copy-P [age_size] <size> Set page size of new database. <size> It Can Be 1024,204 8, 4096,819 2. Set 1024. Storage-pa [ssword] <password> Information Confidentiality -R [eplace_database] There is an existing resource. You can only perform this operation on the user who has this resource. Do not upload the data in use! Stored-role <role> Using a group of Role -Se [Rvice] Copy: Create, use service management. Save: Save, use service management. -T [ransportable] Create portable copies (different production systems and Firebird versions) Replica-U [SER] <username> Information consumer user name-use _ [all_space] Normally, the memory is stored. The data record will be filled in at 80%, and only 100% will be returned (because there is no need to leave a modified space) Back-V [erbose] Indicates the dynamic operation of all gbak upload rows-Y <FILENAME> Repeat all records to a specific issue <FILENAME>. Note: The alias cannot exist before the command line! -Y suppress_output Quiet Mode -Z Release example: normal copy: gbak-v-T-user sysdba-Password "masterkey" dbserver:/DB/warehouse. FDB c: \ Backups \ warehouse. FBK copies and records the outgoing messages of all copies: gbak-v-T-user sysdba-Password masterkey-y c: \ Backups \ warehouse. log dbserver:/DB/warehouse. FDB c: \ Backups \ warehouse. normal FBK memory: gbak-C-v-user sysdba-Password masterkey C: \ Backups \ warehouse. FBK dbserver:/DB/warehouse2.fdb stores an existing resource: gbak-c-r-v-user sysdba-Password masterkey C: \ Backups \ warehouse. FBK dbserver:/DB/warehouse. FDB stores a unique resource: gbak-C-v-mode read_only-use_all_space-user sysdba-Password masterkey C: \ Backups \ warehouse. FBK c: \ files \ warehousedb. when the FDB multi-case documents are large, the documents need to be written in a bit difficult. Therefore, we have copied the materials into many small cases, therefore, saving time is easier than copying data: gbak [Options] <database> <target file 1> <size 1> <target file 2> <size 2>... <target file n> Note: do not specify the size of the last case. because we do not necessarily know how much space is required for storing the last case, it will automatically store the data according to the actual size. in other cases, the size can be bytes (8192), kilbytes (1024 K), megabytes (5 m), or gigabytes (2g) memory callback: gbak-C [Options] <source file 1> <source file 2>... <source file n> <database> the data stored in one or more cases is limited in some systems, or because of performance factors, therefore, a single item is required, it can be divided into several small resources, such as gbak-C [Options] <Source File> <dB file 1> <size 1> <dB file 2> <size 2>... <dB file n> Note: do not specify the size of the last resource. it can be changed to a larger size based on the stored case. size can be given in bytes (8192), kilbytes (1024 K), megabytes (5 m), or gigabytes (2g) the metadata stored in multiple upload cases: gbak-C [Options] <source file 1> <source file 2>... <source file n> <dB file 1> <size 1> <dB file 2> <size 2>... <dB file n>