Results 1 to 6 of 6
  1. #1
    Join Date
    Oct 2012
    Posts
    7

    ISM setup for onbar

    I am trying to set up ISM and onbar as per some tutorials and I am missing something. When running onbar -b -L 0 not much happened, it just sat there.

    .nsr and volume were created in the folder I wish to backup to and /nsr/logs/daemon.log just filled with this:
    11/02/12 08:06:44 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s)
    11/02/12 08:21:45 nsrd: media critical event: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s)
    11/02/12 08:36:45 nsrd: media event cleared: backup to pool 'ISMDiskData' waiting for 1 writable backup tape(s) or disk(s)
    11/02/12 11:06:24 nsrd: media waiting event: backup to pool 'ISMDiskData' waiting for 1 writable backup disk(s)

    Thats the problem, now this is what I did:
    set
    ISM_DATA_POOL ISMDiskData
    ISM_LOG_POOL ISMDiskLogs

    ran:
    Code:
    #ism_startup -init
    #ism_add -admin informix@pasodb1
    $ism_add -device /backups/dbspaces -type file
    $ism_add -device /backups/logfiles -type file
    $ism_op -label /backups/dbspaces -pool ISMDiskData -volume ISMData
    $ism_op -label /backups/logfiles -pool ISMDiskLogs -volume ISMLogs
    $ism_op -mount /backups/dbspaces
    $ism_op -mount /backups/logfiles
    ism_show -devices and ism_show -volumes return nothing while ism_watch returns:
    Code:
    Up Version: Informix_Storage_Manager ISM.2.20.UC1.125-01/26 Server Edition
     Saves: 0 session(s)  Recovers: 0 session(s)
    Device            type     volume
    ckups/dbspaces    file     (none)
    ckups/logfiles    file     (none)
    One thing I read was to add a -force to the -label commands but it made no difference. I am sure I am missing something super simple.

    Thanks

  2. #2
    Join Date
    Sep 2011
    Location
    Pont l'Abbé, Brittany, France
    Posts
    348
    Hi,

    a bit in a hurry now, just to know what version you are using?
    Rumors say that the new release would make the configuration of ISM muuuuuch easier.
    Could you consider waiting a few months and upgrade ?

  3. #3
    Join Date
    Oct 2012
    Posts
    7
    We are using 11.70, as for ISM it is version ISM.2.20.UC1.125 I think. I don't think we can wait since it isn't really my call. He would be happy to use ontape unless I can prove on_bar would be easier in the long run.

  4. #4
    Join Date
    Sep 2011
    Location
    Pont l'Abbé, Brittany, France
    Posts
    348
    by the way, did you check onwsership and permissions of the directories.
    I think they should be set
    owner informix group informix, chmod 770 for directories
    and files should be owner informix group informix, chmod 660

    Not sure, but can you try?

  5. #5
    Join Date
    Oct 2012
    Posts
    7
    I am hoping that may have done it. I had the folders correct, but for some reason the files were root root and 600. On_bar connected to the ism just fine, not sure if I should be worried that the volumes seem to not be labeled in ism_watch and ism_show -volumes has no results still. Thanks again for the help!

    Edit:

    Had to redo the ism_op commands and it looks like it works. All of the files it created have the same permissions as the volume and such did, root owner, root group and 600. Not sure if this is normal or a problem, but it is progress for sure. Thanks again!
    Last edited by bryan.; 11-07-12 at 14:57.

  6. #6
    Join Date
    Oct 2012
    Posts
    7
    I don't want to create a new thread unless I need to, but this issue is in the same ballpark.

    Backups are working fine, its how I would like to manage them that I am having trouble with. Firstly, what I will be doing is taking a level 0 every night which is around 18 gb. In a perfect world, the last three days of backups would reside there for quick access (only 75gb of space free) while the backups also get pushed somewhere else and eventually to tape.

    My attempt at this has been to run:

    Code:
    ism_config -retention 3
    onsmsync
    But the volume continues to grow until I am out of space. Is there anyway to do this in an easy way, or will my backup routine have to be backup, unmount device, copy volume and files, create new volume and remount?

Posting Permissions

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