onsmsync argument: Synchronize with the storage manager catalog (SQL administration API)

Use the onsmsync argument with the admin() or task() function to synchronize the sysutils database and emergency boot file with the storage manager catalog.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-EXECUTE FUNCTION--+-admin-+--(--"onsmsync"------------------->
                     '-task--'                  

>--+---------------------------------------------------------------------------------------+-->
   '-,--"--+-+-----------------------------+--+------+--+------+--+-----------------+-+--"-'   
           | +- -g --number_of_generations-+  '- -s -'  '- -O -'  +- -f --file_name-+ |        
           | +- -t --date_time-------------+                      | .---------.     | |        
           | '- -i --interval--------------'                      | V         |     | |        
           |                                                      '---dbspace-+-----' |        
           '- -b ---------------------------------------------------------------------'        

>--)--;--------------------------------------------------------><

Element Purpose Key considerations
no options Synchronizes the sysutils database and emergency boot file with the storage-manager catalog None.
-b Regenerates both the emergency boot file (ixbar.servernum) and the sysutils database from each other. If the ixbar file is empty or does not exist, onsmsync -b recreates the ixbar file and populates it from the syutils tables.

If the ixbar is not empty and contains object data, onsmsync -b updates the sysutils database and the ixbar file so that they are in sync.

If the ixbar file has entries and the sysutils database has been rebuilt, but is empty because it does not contain data, the onsmsync -b option recreates the sysutils data from the ixbar file.

The -b element is not used with the other onsmsync options. Additionally, it does not synchronize with the storage manager.

dbspace Specifies the storage space or storage spaces to expire If you enter more than one storage space, use a space to separate the names.
-f file_name Specifies the path name of a file that contains a list of storage spaces to expire Use this option to avoid entering a long list of storage spaces. The file name can be any valid UNIX or Windows file name.
-g number_of_generations Retains a certain number of versions of each level-0 backup The latest generation of backups are retained and all earlier ones are expired.
-i interval Expires all backups older than some period of time Retains backups younger than this interval. Backups older than interval are not expired if they are needed to restore from other backups after that interval. Use the ANSI or GLS format for the interval: YYYY-MM or DD HH:MM:SS
-s Skips backups that the storage manager has expired Use this option to skip synchronizing objects that are already expired from the storage manager. The object expiration will be based on other arguments if the -s option is provided.
-O Enforces expiration policy strictly If used with the -t, -g, or -i option, expires all levels of a backup, even if some of them are needed to restore from a backup that occurred after the expiration date. The -O option does not affect logical-log expiration. See Expire all backups.
-t date_time Expires all backups before a particular date and time Retains backups younger than this datetime. Backups older than datetime are not expired if they are needed to restore from other backups after that datetime. Use the ANSI or GLS_DATETIME format for datetime.

Usage

This function invokes the onsmsync utility to synchronize the sysutils database and emergency boot file with the storage manager catalog.

Example

The following example invokes the onsmsync utility and specifies that number of backups retained is 1 and all earlier backup versions are expired:
EXECUTE FUNCTION task("onsmsync", "-g 1");
     

Copyright© 2019 HCL Technologies Limited