Veritas did found troubles with a SAN T3 so it did close its connection to the T3.
Now during boot we have issues that the server will NOT boot if we not send a control-c at steps during boot process
1.) when it comes to
VxVM starting s...
Hi,
I started a vxresize coomand last Friday night to shrink a volume from 800 to 700 GB,
with a df -k it is already down to 700
with vxtask list it shows no task running
only a ps -ef show a running process since Friday
how can I assume that t...
Our system frozen a lot of medias and unfrozen them shows us an ALL tapes:
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -ev 000283
/usr/openv/netbackup/bin/admincmd/bpmedialist -mlist -l -ev 000283
requested media id was not found in NB medi...
We have VEritas Version 5and now the need to increase a volume over 1TB Veritas breaks withVXVM vxassist Error V-5-1-436 Cannot allocat space to grow volume to xxx blocksresize problem V-5-1-4703running vxassist command for volume data so I have to u...
Hi, after reboot th erobot cannot initialized and I see on the OS systembash host# cfgadm -c configure c4cfgadm: Library error: failed to create device node: 500104f0006e46a8: I/O errorOperation partially successful. Some failures seenbash host# cfga...
we are using VxVM 3.5, all others are already on V5 , but this one is 3.5 with Solaris 8
The only other idea I had is to bring it down in single user mode and do a probe-scsi-all to get clean scsi pathes maybe that would help ??
Version is Solaris 8 , and no I have not tried to un-encapsulate the disk.
In the meantime we can boot the machine but Veritas still has issues in finding all pathnames or let me say in working correctly.
After a boot I see just:
root 132 1...
I understand you mean moving volumes from server A to server B ? Are you then using the same disk on the server B as beofre on server A ?Then have a look to vxdeport which deports all information from the volume to the disk. IF so this could it be:ta...
Andy, you may right, we had a lot of error messages which confused me.I now found out that whenever I down drive # (which is the one with the error message)the system was ok and robot could be initialized. So we had a hardware engineer on side which ...
Let me explain before: when I go and reset the robot and bott the server then all drives are ok and robot initialized when I then start backups the first 3 run fine, further more will cause that thesystemmessage"cannot initialize robot"g1bs01 console...
