Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
dcampregher Outstanding Contributor.
Outstanding Contributor.
202 views

Warning: Can not upgrade catalog of medium

Jump to solution

Hi,

 

During the catalog migration, the omnimigrate.pl are showing the error:

Warning: Can not upgrade catalog of medium 621113ac:4e5e92fd:0d3c:0017

Cell Manager in Windows 2008 R2, with 9.04 patches.

Some  medium was migrated but in the major are with this error. Any idea ?

Diogo

-----------
Please assign Kudos
0 Likes
1 Solution

Accepted Solutions
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution

The basic, again ...

 

The MS Anti-Vírus was enabled in the server. Disable the anti-vírus and the conversion was done.

 

Thanks!

Diogo

-----------
Please assign Kudos
0 Likes
11 Replies
Micro Focus Expert
Micro Focus Expert

Re: Warning: Can not upgrade catalog of medium

Jump to solution

Hello

 

Check that global file variable "SupportOldDCBF" is set to 1, The upgrade of DCBF files shall work with this.

C:\ProgramData\OmniBack\Config\Server\Options

Best Regards

 

0 Likes
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution

Hi,

 

The SupportOldDCBF=1 are in  global file.

In the Internal Database awas created one Admin Session for each try to convert, it show all the sessions being imported but at the end of session there are a error.

-----------
Please assign Kudos
0 Likes
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution
[Normal] From: ASM@server.ad.local ""  Time: 11/18/2015 3:00:00 PM
      Processing session from database:
         Session ID:  2013/10/05 0002
         Owner:       BRSBSTE01\ADMINUSER@server.ad.local
         Start time:  10/5/2013 3:30:05 AM
 
[Major] From: ASM@server.ad.local ""  Time: 11/18/2015 3:00:00 PM
      Failed to copy catalog of medium "621113ac:51e523b6:1028:0005".
 
[Normal] From: ASM@server.ad.local ""  Time: 11/18/2015 3:00:00 PM
      Upgrade of Detailed Catalog Binary Files ended successfully. 1 file(s) upgraded.
-----------
Please assign Kudos
0 Likes
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution

 

The media in case the error now have two DCBF files, an older in DB40 a new in DB80.

-----------
Please assign Kudos
0 Likes
Absent Member.. svollrat Absent Member..
Absent Member..

Re: Warning: Can not upgrade catalog of medium

Jump to solution

the first one in your screenshot is the attempt to upgrade the catalog, if IDB considers is as unclean the DB-Check and DCBF-Purge should remove it.

Catalog Upgrade only works if everything is perfect, slight glitches in old Filesnames-Part and nothing works.

If you haven't done a Export/Import before upgrading, cleaning out all unrequired data and other inconsistencies you likely end up with that.

Only two Options I know are keeping the old Catalog and db40 Part until the affected media are expired or newly Import them, reading the Catalog directly from Tape.

0 Likes
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution

Hi,

 

I change the IDB to another server before the upgrade so i done the export/import, remap_dcdirs, fixmpos and omnidbcheck -extended with no errors.

There are tapes with permanent protection  and becase this, wait aren't a option for us.

 

Diogo

-----------
Please assign Kudos
0 Likes
Absent Member.. svollrat Absent Member..
Absent Member..

Re: Warning: Can not upgrade catalog of medium

Jump to solution

any particular Infos on the omnimigrate-Logs that may indicate why the Catalog-Upgrade fails? That could help fixing the cause.

Don't think there is much that can be done in place without asking the Support for help.

Best but longest solution in my opinion is still cleaning all those invalid DCBFs and getting the Catalog directly from Tape. Has also the additional benefit that you verify the Data is still readable.

0 Likes
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution

Hi,

In the omnimigrate logs there are no conclusive infos but in the debug.log file there is one  entry for each try to omnimigrate.pl migration:

11/19/2015 11:24:23 AM  ASM.3252.3808 ["/lib/cmn/win32io.c $Rev: 49013 $ $Date:: 2015-07-03 07:58:30":353] A.09.00 b104

 [OB2_OpenFile] CreateFileW(filename:C:/ProgramData/OmniBack/tmp/621113ac_4fe8c37c_0d84_0031.fdb) failed, errno=[5] Access is denied
 
The user under of DP services is a local Administrator of server and is in the Admin group of DP.
 
The file 621113ac_4fe8c37c_0d84_0031.fdb was created but with 0 bytes. The cleanup remove the files generated by the process.
 
Idea ?
-----------
Please assign Kudos
0 Likes
Absent Member.. svollrat Absent Member..
Absent Member..

Re: Warning: Can not upgrade catalog of medium

Jump to solution

w2k8 and above is a B*tch, Admin doesn't mean you can do everything :-/

Check the Permissions of the tmp-Folder and in doubt let also LocalSystem and Users write and delete there.

Also it could be that you don't have enough space there, just in case Windows reports incorrect status.

0 Likes
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution

Full Control for all users envolved.

There are 23GB reported by the Windows as free space.

 

Very weird !

 

 

-----------
Please assign Kudos
0 Likes
dcampregher Outstanding Contributor.
Outstanding Contributor.

Re: Warning: Can not upgrade catalog of medium

Jump to solution

The basic, again ...

 

The MS Anti-Vírus was enabled in the server. Disable the anti-vírus and the conversion was done.

 

Thanks!

Diogo

-----------
Please assign Kudos
0 Likes
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.