Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Tripoint HPUX A Absent Member.
Absent Member.
2679 views

IDB Defrag

Jump to solution

Hi,

 

Can someone confirm if this is the correct procedure when performing an IDB defrag?

 

Our Cell Manager is running 6.21 on Windows 2008 R2 Sp1 

 

  1. Ensure that the last IDB backup was successful – note down the tape number in case a restore is required
  2. Ensure there are no backups running:
    omnistat (will show any active tasks)
    omnisv –stop (stops the DP services)
  3. Copy C:\Program Files\Omniback to C:\temp\Omniback
  4. Start the Data Protector services and shut down omnitrig (omnitrig –stop) to ensure no scheduled backups are started.
  5. Double-check that no backups are running by running an “omnistat”.
  6. Ensure that no Data Protector manager GUI sessions are open and then run the following commands:
    omnidbutil -purge –dcbf
    omnidbutil –fixmpos
    omnidbutil -purge_failed_copies
    omnidbutil -purge -filenames –force
  7. The omnistat command can be used to monitor the progress of the “omnidbutil -purge -filenames –force” command.
  8. omnidbutil –clear
  9. Once the above commands have been completed, proceed with the IDB export to files:
    omnidbutil -writedb -cdb C:\DB\ -mmdb C:\DB
  10. When prompted, confirm the exports for the various components.
  11. After the IDB export you will need to make a copy of the following directories as per the command prompt advises:
    "C:/Program Files/OmniBack/db40/msg"
    "C:/Program Files/OmniBack/db40/dcbf"
  12. Copy these to a temporary location as they will need to be copied back to their original location after the import
  13. Once the exports have completed, perform a re-initialize of the IDB:
    omnidbinit
  14. Then re-import the export dumps taken earlier:
    omnidbutil -readdb -cdb C:\DB\ -mmdb C:\DB
  15. After the import is complete you will need to copy the following directories back to their original location:
    "C:/Program Files/OmniBack/db40/msg"
    "C:/Program Files/OmniBack/db40/dcbf"
  16. Once the imports have completed remove invalid references to DCBF. This should be run following IDB recovery:
    omnidbutil -remap_dcdir
  17. Restart the data protector services.
0 Likes
1 Solution

Accepted Solutions
Absent Member.. spmm07 Absent Member..
Absent Member..

Re: IDB Defrag

Jump to solution

Hi,

Your detailed plan looks good and yes, in Win2008 and R2, by default IDB is located in C:\ProgramData\OmniBack\ directory.

So, step3 needs to be modified as:

3.Copy C:\ProgramData\OmniBack to C:\temp\Omniback

 

Also, you may have to add a trailing "\" for mmdb export location for step 9 and 14: omnidbutil -writedb -cdb C:\DB\ -mmdb C:\DB\. Not a must thing to consider, but just to be careful.

Regards,
Prakasam S

View solution in original post

0 Likes
5 Replies
Tripoint HPUX A Absent Member.
Absent Member.

Re: IDB Defrag

Jump to solution
the above procedure was used when our cell manager was on windows 2003, but i believe with windows 2008 and r2 servers data protector stores information in C:\ProgramData\OmniBack as well.

So i think with step 11 and 15 we need to add C:\ProgramData\OmniBack\db40\msg and C:\ProgramData\OmniBack\db40\dcbf to the list of directories to take copies of
0 Likes
Absent Member.. spmm07 Absent Member..
Absent Member..

Re: IDB Defrag

Jump to solution

Hi,

Your detailed plan looks good and yes, in Win2008 and R2, by default IDB is located in C:\ProgramData\OmniBack\ directory.

So, step3 needs to be modified as:

3.Copy C:\ProgramData\OmniBack to C:\temp\Omniback

 

Also, you may have to add a trailing "\" for mmdb export location for step 9 and 14: omnidbutil -writedb -cdb C:\DB\ -mmdb C:\DB\. Not a must thing to consider, but just to be careful.

Regards,
Prakasam S

View solution in original post

0 Likes
André Beck
Visitor.

Re: IDB Defrag

Jump to solution

Hi,

 

the new 2008R2 gotcha was already mentioned. If you are just doing that for the stated purpose (compacting the IDB after the filename purge so as to speed it up significantly), you can avoid steps 11/12 (copying binary files somewhere safe), 13 (omnidbinit) and 15 (copy binary files back). Specifically avoiding 13 makes things simpler, as you don't have to rebuild anything regarding IDB files and extensions. The IDB is still truncated and filled sequentially from the start on the readdb step, so there really is no sense in omnidbinit here. Not copying away and copying back the binary files also makes sense as they are laying around unchanged anyway, and it really saves time and space. The procedure you post is complete even for the case where you move everything to a blank drive, and there the additional steps make sense. But not for just in-place IDB health maintenance.

 

BTW, to get a rough feeling of how long it will take, the filename purge and the writedb will take roughly as long as an IDB check each, the import will be faster (provided there was anything purged in this or a previous purge session). So just expect two to three times the IDB check time you saw before the maintenance. It really depends on whether you did a filename purge ever before without compacting, as that makes the IDB really slow (I've seen 4h check times for moderately sized IDBs of like 20GB).

 

HTH,

Andre.

0 Likes
Tripoint HPUX A Absent Member.
Absent Member.

Re: IDB Defrag

Jump to solution

Just on the new location of the IDB etc in C:\ProgramData, what does that mean for C:\Program Files\Omniback ?  As i still have all the old directories intact there occupying a large portion of drive space, are these still required?
C:\ProgramData\Omniback = 29GB
C:\Program Files\Omniback = 8GB
i'm running a physical system with low disk space so if i can claim back that 8GB from the old location that would be rather useful.

Updated steps:
Procedure Steps for Windows 2008/R2 Cell Manager

  1. Ensure that the last IDB backup was successful – note down the tape number in case a restore is required
  2. Ensure there are no backups running:
  3. omnistat (will show any active tasks)
  4. omnisv –stop (stops the DP services)
  5. Copy C:\Program Files\Omniback & C:\ProgramData\Omniback to C:\temp\DP
  6. Start the Data Protector services and shut down omnitrig (omnitrig –stop) to ensure no scheduled backups are started.
  7. Double-check that no backups are running by running an “omnistat”.
  8. Ensure that no Data Protector manager GUI sessions are open and then run the following commands:
  9. omnidbutil -purge –dcbf
  10. omnidbutil –fixmpos
  11. omnidbutil -purge_failed_copies
  12. omnidbutil -purge -filenames –force
  13. The omnistat command can be used to monitor the progress of the “omnidbutil -purge -filenames –force” command.
  14. omnidbutil –clear
  15. Once the above commands have been completed, proceed with the IDB export to files:
  16. omnidbutil -writedb -cdb C:\DB\ -mmdb C:\DB\
  17. When prompted, confirm the exports for the various components.
  18. After the IDB export you will need to make a copy of the following directories as per the command prompt advises:
  19. "C:/Program Files/OmniBack/db40/msg"
  20. "C:/Program Files/OmniBack/db40/dcbf"
  21. "C:/ProgramData/OmniBack/db40/msg"
  22. "C:/ProgramData/OmniBack/db40/dcbf"
  23. Copy these to a temporary location as they will need to be copied back to their original location after the import
  24. Once the exports have completed, perform a re-initialize of the IDB:
  25. omnidbinit
  26. Then re-import the export dumps taken earlier:
  27. omnidbutil -readdb -cdb C:\DB\ -mmdb C:\DB\
  28. After the import is complete you will need to copy the following directories back to their original location:
  29. "C:/Program Files/OmniBack/db40/msg"
  30. "C:/Program Files/OmniBack/db40/dcbf"
  31. "C:/ProgramData/OmniBack/db40/msg"
  32. "C:/ProgramData/OmniBack/db40/dcbf"
  33. Once the imports have completed remove invalid references to DCBF. This should be run following IDB recovery:
  34. omnidbutil -remap_dcdir
  35. Restart the data protector services.
Highlighted
Absent Member.. spmm07 Absent Member..
Absent Member..

Re: IDB Defrag

Jump to solution

The C:\Program Files\Omniback directory contains the DP executables and you can remove other old directories from it(db40, config, depot, etc.,). Before you delete, ensure the database files are located in C:\ProgramData.

Regards,
Prakasam S
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.