Data Protector - Passion for Data Protection

data-protector.org

Cannot Create Integration Backups when Patch DPWIN_00483 is installed

Posted on by

Once you installed the patch DPWIN_00483 (VEPA patch) you are no longer able to create new integration backups (Exchange, SQL, …). Withhin GUI you are not able to browse for instances. The bug comes from changed manager.exe through patch DPWIN_00483. As a workaround you may use the JAVA GUI where the bug was not seen so far. HP also released an advisory – see corresponding section.

Initialization of medium failed – filelibrary full

Posted on by 3 Comments

The error Initialization of medium failed is shown when the Filelibrary is full or almost full (one or more mountpoints / folders in filelibrary). If you did not install the GR Patches from July 2010, you may also see a lot of media with blue question mark withhin the mountpoint from your filelibrary. In addition it has been seen that the file cart.txt is quite large when you would do an export of MMDB (omnidbutil -writedb -mmdb Verzeichnis).
As a first starting mount you may want to increase diskspace for the mountpoint or you can migrate media from the filelibrary to another media off the filelibrary to get free diskspace. As a second step you may want to try to format the media with the blue question mark.
If you still encounter problems try following procedure:

  • Generate a list of filedepot files from the correspondig mountpoint
  • Download the filelibrary with omnidownload -library Libraryname -file Filename
  • Edit the downloaded file and modify the entries from your generated list, delete all old entries before and use the same format.
  • Upload the filelibrary with omniupload -modify_library Library -file Filename

    • In any case you should install the lateste patches (current: GR Patches from July 2010) as the error is already resolved with these patches.
    If you still encounter problems I recommend to completly empty the file library (migrate all media from involved file library to another media off the filelibrary) and to remove not needed (or wrong) entries from cart.txt. What has to be deleted in cart.txt is not explained here, as this way is not supported. For some bucks I take over this work in a remote session.

    SystemState Backup Windows – Error [81:52]

    Posted on by 3 Comments

    [Critical] From: VBDA@CLIENT "CONFIGURATION:" Time: 21.09.2010 09:20:32
    [81:52] /CONFIGURATION
    Not a valid mount point => aborting

    However following the link will not help at all. In file debug.log no usefull informatino is stored, furthermore the file autodr.log is not created, as the backup was aborted. In general a reboot might help, however might no be needed. In my case I analysed the server in more detail and found in <omnihome>\tmp\config  a previous created backup of CONFIGURATION (which was aborted). As solution I deleted all stuff in <omnihome>\tmp\config and backup of the systemstate of the Windows server was working as expected again.