All Data Protector Practitioners Forum posts

Sebastian,

This file is also generated when the backup is not executing. I would like to supress this. please suggest me.

If i change the file depot size to 100 what change could i observe, please highlight

It is not possible, that depots are created without a BMA process running. During backup the depot can grow up to 100 GB before the next one is created. Smaller backups will not require more capacity on disk as before. Please check omnistat command for running sessions and the Task Manager (Windows) or ps command (UNIX) for any roaming bma processes. What Data Protector release is this? omnisv -version and omnicheck -patches on the Cell Manager will help.

Regards,
Sebastian Koehler

What is the operating system of the MIP server? You Cell Manager is running Windows 2008, right?

Regards,
Sebastian Koehler

our client system (MIP) is red hat linux 5.4 and the data protector installed system is windows 2008 server

Please execute those commands on the MIP server to see what is installed and if it is running. Is there an UNIX installation server in this cell?

rpm -qa | grep OB2
/opt/omni/lbin/dma -version
telnet localhost 5555

Regards,
Sebastian Koehler

You have a mixture of Data Protector A.06.11 and A.06.20 installed which is not supported. I would remove the agent complely and start from scratch. Again, is there an UNIX Installation Server available in this cell? Check GUI => Clients => Installation Servers?

If not, we need to use the correct UNIX/Linux media kit for the Data Protector release. Please share the following output from Cell Manager.

omnicheck -patches
omnisv -version

Regards,
Sebastian Koehler

If you want the client back in the cell you need to follow my instructions step by step. The procedure is required for UNIX push installation to work from Installation Server bidevqly to client miprd (without any software installed). Never ever use an IP address where a hostname is required! This means Use miprd during the Add clients dialog or it will fail.

Regards,
Sebastian Koehler

sorry for not following your instruction properly, so now i will remove the miprd from the cell manager and will try to add the client using MIPRD hostname.

regards

Narendran

i tried the steps to delete the client in miprd server but getting the same username and password error.

Sebastian.Koehler wrote:
On bidevqly create or edit /opt/omni/.omnirc and make sure it contains OB2_SSH_ENABLED=1
On bidevqly check as root the content of /root/.ssh folder for any id_dsa.pub or id_rsa.pub file; if the file does not exist run ssh-keygen -t rsa -b 2048 and save it without any passphrase
On bidevqly run ssh-copy-id -i /root/.ssh/id_rsa.pub root@miprd and enter the password, then login using ssh root@miprd that should work without any prompts
Return to Data Protector GUI and try the push installation again

You need to run the commands on host bidevqly which is your Installation server!

Regards,
Sebastian Koehler

i did the same things in the bidevqly server but still the error persist.

Hi ,

thanks for your answer.

while I waiting your answer, I try to restore to the C: and it work (the default location, F:, was a disk that is crashed.

So its not very easy to find enough space.

thanks for you answer.

Are you able to ssh root@miprd without any prompts showing up? Please share /var/opt/omni/log/IS_install.log from bidevqly.

Regards,
Sebastian Koehler

Please use the Accept Solution button next to my post and assign a Kudo (thumbs up).

Regards,
Sebastian Koehler

i can able to ssh root@miprd without any prompts and i am unable to attach the log file with this post, since it is in .log format.

I can't explain why it fails, but we can try a manual installation. Have you a Data Protector A.06.11 HP-UX or Linux installation media ready? You can mount it on the server to /mnt for example and run /mnt/LOCAL_INSTALL/omnisetup.sh -install da

If not, we can copy the files from the Installation server. In that case I need to know the architecture of miprd (uname -a output).

Regards,
Sebastian Koehler

we dont have the media ready, so i will give the uname -a output

Hello.

I see that the DP support for XenServer was dropped in the last releases. What are the recomendations for customers that still trust on old versions of DP for XenServer backup?

We will install the bare minimum and add the rest of the agent remotely from Installation server (which should always work).

Run this from bidevqly. If there is a error in the path for the scp commands you might need to adjust the path.

scp /opt/omni/databases/vendor/omnicf/gpl/x86_64/linux-x86-64/A.06.11/packet.Z miprd:/tmp/core.Z
scp /opt/omni/databases/vendor/da/gpl/x86_64/linux-x86-64/A.06.11/packet.Z miprd:/tmp/da.Z
ssh root@miprd
cd /tmp

# I can't remember if uncompress was still required on A.06.11 packages
uncompress core.Z
mv core core.rpm
rpm -Uvh core.rpm

uncompress da.Z
mv da da.rpm
rpm -Uvh da.rpm

If this works ok try to import the client from GUI.

Regards,
Sebastian Koehler

Latest Images