Please try to open E:\programdata\omniback\db40\dcbf in Windows explorer first. Does the path exist?
Regards,
Sebastian Koehler
↧
Re: Data Protector - Database internal error
↧
Re: Expired media not moving to free pool after upgrade from DP8.14 to DP9.07
As a workaround run omnidbutil -free_pool_update manually. Ask support QCCR2A69503_HF1. This should resolve the issue in omnitrig.
Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.
Regards,
Sebastian Koehler
↧
↧
Re: Data Protector - Database internal error
Sebastian ,
The path exists and is correct .
The graph shows that I have no problem with lack of space for dcbf.
↧
Re: Expired media not moving to free pool after upgrade from DP8.14 to DP9.07
Thanks Sebastian, we will check this out! I will update this thread on my findings.
↧
Re: ZDB : [ 236:52] Failed to resolve a storage volume on the host
Many thanks , i have also the same impression that backup host is not able to read device information.
I've attached the logs. Please rename extension of the file to .7z.
DPX
↧
↧
Re: Expired media not moving to free pool after upgrade from DP8.14 to DP9.07
So running the omnidbutil command manually works.
Also checked with Support and there is a new DP9.07 release b110, but unfortunately the fix listed above is not a part of that release. So I have to open a case to get the fix since to deliver a fix lab approval is needed.
Stay tuned...
↧
Re: Data Protector - Database internal error
SantaCasa wrote:
8/23/2016 9:38:53 AM DBSM.1688.2628 ["/lib/cmn/win32io.c $Rev: 23060 $ $Date:: 2011-08-08 16:32:55":783] A.07.00 b106
[OB2_StatFile] FindFirstFile failed, errcode=123 [file=/E:/ProgramData/OmniBack/db40/dcbf]8/23/2016 9:38:53 AM DBSM.1688.2628 ["/db/dc/dcbf/dcbf.c $Rev: 39452 $ $Date:: 2013-10-10 20:51:21":1698] A.07.00 b106
[dcbf_mediumFileDirectories_add] failed to stat mbf [123]: '/E:/ProgramData/OmniBack/db40/dcbf'
I don't understand why DBSM fails to read the directory content. Have you tried omnidbcheck -bf?
Regards,
Sebastian Koehler
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
Thank you for the reply.
How do we mount the iso file in loop back mode in HP-UX 11.31.
Is it possible ?
Kindly let me know how i can do the same
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
There are several optiions. Please refer to this post, since this depends on the HP-UX 11.31 packages installed. MP/ILO mount is the best choice.
SUMMARY: Three simple methods to mount ISO files on HP-UX 11.31
http://community.hpe.com/t5/System-Administration/SUMMARY-Three-simple-methods-to-mount-ISO-files-on-HP-UX-11-31/td-p/5201873
Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.
Regards,
Sebastian Koehler
↧
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
Tannk you i was able to moun the iso .
Will try installing the Dp 9 and update you the status
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
hi i was able to succesfully upgrade the DP to 9
↧
Re: ERROR: The "checkinstall" script for "DATA-PROTECTOR" failed while upgradi
Good news! Please install the latest patch bundle (9.07 plus the 9.07_110 patches) that can be obtained from the SSO portal and mark this topic as resolved. This helps others to find the right solutions.
Regards,
Sebastian Koehler
↧
Re: ZDB : [ 236:52] Failed to resolve a storage volume on the host
Hi,
From logs I was able to determine:
- Replica is successfully created
- Replica is successfully presented
- After presentation rescan is initiated on backup host
- Seems that after rescan replica is still not seen on backup host.
Would suggest following:
- On backup host set following 2 omnirc variables:
ZDB_DELAY_BEFORE_RESCAN=120
ZDB_DELAY_AFTER_RESCAN=120
- With these settings you will get 4 minutes to determine if volume/replica is visible on backup host after presentation is made.
Would suggest that you connect to backup host, and perform rescan of FC manually (rescan-scsi-bus.sh)
And determine that replica is visible on backup host.
Could be that delay itself will give enough time to backup host to recognize the new volume.
If you still cant find volume on the backup host then I suggest you check your settings on backup host.
- Create replica manually on 3PAR host
- Present it manually to backup host
- Rescan and try to find volume on backup host
- Make sure that is visible with “multipath -ll” command
/etc/multipath.conf is where I would start looking.
I have seen cases where “find_multipaths = yes” setting was preventing backup host to see volume.
Please let me know the findings & regards
Ales
↧
↧
Re: ZDB : [ 236:52] Failed to resolve a storage volume on the host
Many thanks Ales. It was issue with multipath configuration on the backup host.
Regards,
DPx
↧
Re: Data Protector - Database internal error
Sebastian,
Medium ID: Actual Size Header Size Check
========================================================================
f001010a:55018bb3:0ea8:00014695816846958168 OK
f001010a:52bc2ab7:0ba0:000118078881807888 OK
f001010a:55926da8:07d8:00016706067060 OK
f001010a:574f2d9b:0fd4:00012487851224878512 OK
f001010a:4cd9498d:0d28:00014464797244647972 OK
f001010a:575adea1:10b0:000135513163551316 OK
f001010a:567aa73a:11a8:00016579929265799292 OK
f064a8c0:4ac652fc:0608:000118665401866540 OK
d201010a:473349fb:01fc:000124013322401332 OK
f001010a:567ae55a:05b0:00012801116428011164 OK
f064a8c0:4a39327f:0ae8:000119914041991404 OK
f001010a:55927466:1040:000112352761235276 OK
f064a8c0:4b0edcd2:0ba8:00011969436019694360 OK
f001010a:55926c28:1184:000122465682246568 OK
f064a8c0:4aa166aa:0e38:000119592241959224 OK
f001010a:574f2c08:0a10:00018152565281525652 OK
f001010a:5716121a:1294:000173061767306176 OK
f001010a:5720c0df:0ef4:00019346699293466992 OK
f064a8c0:4b23f8de:05ec:0001254957396254957396 OK
f001010a:54330ad1:01e8:00013490034900 OK
f001010a:55926da3:0d40:0001280408280408 OK
f001010a:4ed7807c:0a44:00017778077780 OK
f001010a:567a9ff2:16cc:000178284287828428 OK
f064a8c0:4b23f7db:0bc0:000141416324141632 OK
f001010a:550194b5:0ffc:00012673526426735264 OK
f001010a:55926cc4:06f0:00015634056340 OK
f001010a:567ae639:0fbc:00012199445621994456 OK
f064a8c0:47f3923c:08a8:00011792982817929828 OK
f001010a:57b48c80:116c:000191729172 OK
d201010a:47335eeb:0a8c:00012203622036 OK
f001010a:559271a4:12f4:00016277262772 OK
f001010a:5256d5cc:088c:00011653529616535296 OK
f064a8c0:4b2402e0:0f48:000125413442541344 OK
f001010a:545133e6:0a6c:00013942039420 OK
f064a8c0:4b23f5e4:0788:0001238283320238283320 OK
f001010a:57602907:1214:0001210153272210153272 OK
f001010a:567ae6ce:0e54:00012271830822718308 OK
f001010a:556c9531:0cd0:00013768966437689664 OK
f001010a:4e08c1c4:05d4:000133264323326432 OK
f001010a:523adc6f:09ac:0001255908752255908752 OK
f001010a:5591a068:115c:0001628788628788 OK
f001010a:567ae756:1594:00014728085247280852 OK
f001010a:567ae88a:0bb8:0001301519660301519660 OK
f064a8c0:4aa165ad:0e24:0001469320469320 OK
f001010a:5716129c:080c:00014263220442632204 OK
f001010a:575ac9df:1324:00013275632756 OK
f001010a:4cd94c00:0c2c:000121141162114116 OK
f064a8c0:4b50bf11:0cb8:000195341769534176 OK
f064a8c0:4aa165d6:02d0:00011010458810104588 OK
f001010a:567aa08d:10b4:00012427399624273996 OK
f001010a:55019535:0478:00011266087212660872 OK
f064a8c0:47f3b2a9:0c68:000168473406847340 OK
f064a8c0:4b0ee061:05d4:000148844884 OK
Check has finished : 0 errors reported
DONE!
↧
3PAR ZDB with "To disk+Tape"
Hello!
I have prepared our fileserver (Windows 2012R2 with GPT-disk) for backup up with ZDB. This is running well. The Snapshots are created at 3PAR.
But when I want to backup the date to tape I got following error:
[Warning] From: SMISA@it-daten1.sbg.salzburg-ag.at "SMISA" Time: 24.08.2016 13:09:21
[236:2504] Disk \\.\PHYSICALDRIVE4 is resolved as Windows GPT Disk (unsupported type).
...
[Warning] From: VBDA@it-hpcm11.sbg.salzburg-ag.at "I: [daten0_daten_i]" Time: 24.08.2016 13:20:54
[81:77] c:\mnt\<Mountpoin>\<Filename>
Cannot open: ([1920] The file cannot be accessed by the system. ) => not backed up.
during backup when LUN ist mouted to c:\mt\... I can browse the dircectories without problems.
what can this be?
rg
Hansi
↧
Re: 3PAR ZDB with "To disk+Tape"
Hi,
Please do check support matrices. GPT disks are not supported together with ZDB.
Regards Aleskol
↧
↧
RMC error while running a backup job in cell manager
Hi all,
I'm getting an error in cell manager [version 9.07 -OS RHEL 6.8] while running a backup job using RMC [Snapshot+disk].
error is :
"Storage systems with following serial numbers are not found on the RMC server"
did anyone face this issue ?
connectivity is Ok between RMC , 3par, cell manager.
storage is configured in RMC and online.
RMC server is added in cell manager
Thanks,
dpx
↧
Re: RMC error while running a backup job in cell manager
Hi dpx,
what is the 3PAR model and 3PAR OS version? Which RMC version are you running?
Regards,
Sebastian Koehler
↧
Re: Data Protector - Database internal error
Are you able to run omnidbcheck -extended? This will take some time. If any errors show up, run omnidbutil -fixmpos and omnidbutil -remap_dcdir.
Regards,
Sebastian Koehler
↧