Configure backint-related parameters
Before you can start using Backint with your SAP ASE Database you will need to ensure that following configuration options are configured in your server:
Topics
Create a dump configuration
In order to make it easier for backup adminsitrator to launch backups with specific settings, it is a best practice to create dump profiles. We can create as many Dump Profiles as we want, each one with different settings. This can be useful when we want to use, for example, one profile for Full Backups, other for Incremental Backup, another one for logs backups, and so on.
_101> use master_102> go_10_101> sp_config_dump_10 @config_name = '<profile_name>',_10 @ext_api = 'emory::compression=<compression_level',_10 @num_stripes = '<int>',_10 @blocksize = '16384'_102> go
Use one of the following examples to create your dump configuration file. You can adapt these parameters to any value that better fits your needs:
_101> use master_102> go_10_101> sp_config_dump_10 @config_name = 'emory_S8',_10 @ext_api = 'emory::',_10 @num_stripes = '8',_10 @blocksize = '16384'_102> go
_101> use master_102> go_10_101> sp_config_dump_10 @config_name = 'emory_S8_C5',_10 @ext_api = 'emory::compression=5',_10 @num_stripes = '8',_10 @blocksize = '16384'_102> go
_101> use master_102> go_10_101> sp_config_dump_10 @config_name = 'emory_S4_C1',_10 @ext_api = 'emory::compression=1',_10 @num_stripes = '4',_10 @blocksize = '16384'_102> go
Ensure that the dump profile has been properly created you can list the existing dump profiles by executing the following command:
_101> use master_102> go_101> sp_config_dump_102> go
To view the configuration details of a specific dump profile, execute the following command:
_101> use master_102> go_101> sp_config_dump <profile_name>_102> go
::: details Expand to see an output example
_10 optionname optionvalue_10 ----------------- ---------------------_10 ext_api emory::compression=5_10 num_stripes 8_10 blocksize 65536
:::
Configure database specific options
In this section you will find the specific configuration settings modifiable for ASE.
All the modifiable values will be listed in the Specific Database configuration for ASE database section in Backint menu:
_10? Backint: [Use arrows to move, enter to select, type to filter]_10 Storage Providers profiles_10 Data storage providers for backups & restores_10> Specific Database configuration for ASE database_10 License Software_10 Logging settings_10 Syntax Backups Dashboard_10 Backups Lifecycle_10 Debug traces_10 Exit
Sybase IO Block Size
By default, the value of block size is set at 16 KB. You can keep increasing the value of block size by multiple of 2 KB till you get a higher I/O during dump and load operations.
It is a best practice to set the block size as 16 KB.
If you need to change this value, follow these steps:
-
Enter the proper section from the menu:
_10? Select action to perfom: [Use arrows to move, enter to select, type to filter]_10> Sybase IO Block Size_10Return -
Select the desired IO Block Size:
_10? Select action to perfom: Sybase IO Block Size_10? Select Sybase IO Block Size (change only under supervision): [Use arrows to move, enter to select, type to filter]_104096 bytes_108192 bytes_10> 16384 bytes_1032768 bytes -
You can now select Return and Exit to save the configuration if no other action should be taken.
The following settings should be applied to your SAP ASE Database:
To perform all the following actions your will need to connect to your SAP ASE database ISQL command line tool.
_10isql -U sapsa -P <your password> -S <SAP SID> -X
-
Check Database Page Size. The recommended value for creating dump configuration settings should be
16384_101> select @@maxpagesize_102> go_10_10-----------_1016384 -
Activate Database Logging. In order to be able to recover a database with Point In Time options, yu must activate database logging.
_101> exec master..sp_dboption D04, 'trunc log on chkpt', false_102> go -
Enable Dumphistory File. To enable the
dump historyfile, execute the following commands:_101> use master_102> go_101> sp_configure 'enable dump history', 1_102> go_101> sp_configure 'dump history filename', 1, 'dumphist'_102> gotipTo ensure that the proper parameters have been activated you can list the current configuration by executing the following commands.
_111> sp_configure 'dump history filename'_112> go_11Parameter Name Default Memory Used Config Value Run Value Unit Type_11--------------------- ----------- ----------- ------------ ------------ -------------------- --------------------_11dump history filename dumphist 0 dumphist dumphist name dynamic_11_111> sp_configure 'enable dump history'_112> go_11Parameter Name Default Memory Used Config Value Run Value Unit Type_11--------------------- ----------- ----------- ------------ ------------ -------------------- --------------------_11enable dump history 0 0 1 1 switch dynamic -
List Dumphistory File contents. To list the current
dump historyfile contents, you can execute the following commands:_101> sp_dump_history_102> go -
Result:
_24DUMP_24----_24Dump_Type Dbid Database_name Stripes Dump_instant File Server_name Compression_lvl Password Status Label Dump_date_24----------- ------ -------------- ------- --------------------------- ------------------------------------------------- ----------- --------------- -------- -------- ----- --------------------------_24DATABASE 4 D04 4 May 22 2020 9:41:29:070AM emory::compression=-2::D04.DB.20200522.093515.000 * 0 no Success * May 22 2020 9:41:33:096AM_24DATABASE 4 D04 4 May 22 2020 9:41:29:070AM emory::compression=-2::D04.DB.20200522.093515.001 * 0 no Success * May 22 2020 9:41:33:096AM_24DATABASE 4 D04 4 May 22 2020 9:41:29:070AM emory::compression=-2::D04.DB.20200522.093515.002 * 0 no Success * May 22 2020 9:41:33:096AM_24DATABASE 4 D04 4 May 22 2020 9:41:29:070AM emory::compression=-2::D04.DB.20200522.093515.003 * 0 no Success * May 22 2020 9:41:33:096AM_24DATABASE 4 D04 4 May 22 2020 11:28:44:076AM emory::compression=9::D04.DB.20200522.105442.000 * 0 no Success * May 22 2020 11:29:29:353AM_24DATABASE 4 D04 4 May 22 2020 11:28:44:076AM emory::compression=9::D04.DB.20200522.105442.001 * 0 no Success * May 22 2020 11:29:29:353AM_24DATABASE 4 D04 4 May 22 2020 11:28:44:076AM emory::compression=9::D04.DB.20200522.105442.002 * 0 no Success * May 22 2020 11:29:29:353AM_24DATABASE 4 D04 4 May 22 2020 11:28:44:076AM emory::compression=9::D04.DB.20200522.105442.003 * 0 no Success * May 22 2020 11:29:29:353AM_24DATABASE 4 D04 0 May 22 2020 11:30:06:163AM dump.error * 0 no Error May 22 2020 11:30:06:163AM_24DATABASE 4 D04 4 May 22 2020 11:34:45:076AM emory::::D04.DB.20200522.113046.000 * 0 no Success * May 22 2020 11:34:53:513AM_24DATABASE 4 D04 4 May 22 2020 11:34:45:076AM emory::::D04.DB.20200522.113046.001 * 0 no Success * May 22 2020 11:34:53:513AM_24DATABASE 4 D04 4 May 22 2020 11:34:45:076AM emory::::D04.DB.20200522.113046.002 * 0 no Success * May 22 2020 11:34:53:513AM_24DATABASE 4 D04 4 May 22 2020 11:34:45:076AM emory::::D04.DB.20200522.113046.003 * 0 no Success * May 22 2020 11:34:53:513AM_24_24CONFIG_24------_24_24ALTER DATABASE_24--------------_24(return status = 0)
High Availability configuration
Backint has no explicit compatibility for a Sybase database system with High Availability configuration.
However, there is a setup you can complete to achieve this:
- Create one bucket for each cluster node
- Install Backint in each node
- Configure Backint to store backups each node to one different bucket
- Execute backups only for the active node
- Execute Transaction Log backups for all nodes