Results 1 to 2 of 2
  1. #1
    Join Date
    May 2006
    Waco, KY

    Question Unanswered: Backup much cpu on Solaris


    We have planned to do backups using both BCVs and the DB2 utility (insurance) for our new system. Our parent company is concerned about the cpu the backup utility will take.

    I read on the web that if we use the compression with it, it will take alot of cpu cycles. What about if we aren't using compression?

    The system is 24x5, main server has 800gb in db. Other servers have 180gb and 50gb.

    If anyone has links to articles on this, I would really appreciate it.


  2. #2
    Join Date
    May 2003
    In version 8.2 you can throttle the backup (see backup database in the Command Reference manual):

    UTIL_IMPACT_PRIORITY priority Specifies that the backup will run in throttled mode, with the priority specified. Throttling allows you to regulate the performance impact of the backup operation. Priority can be any number between 1 and 100, with 1 representing the lowest priority, and 100 representing the highest priority.

    If the UTIL_IMPACT_PRIORITY keyword is specified with no priority, the backup will run with the default priority of 50. If UTIL_IMPACT_PRIORITY is not specified, the backup will run in unthrottled mode. An impact policy must be defined by setting the util_impact_lim configuration parameter for a backup to run in throttled mode.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts