Hi,
Was this solved. This needs configuration as outlined in Integration guide and rightly suggested by Sebastian.
Regards
tech88kur
Hi,
Was this solved. This needs configuration as outlined in Integration guide and rightly suggested by Sebastian.
Regards
tech88kur
[Critical] From: VBDA@srvustxigppvm2 "D: [New Volume]" Time: 7/8/2016 2:29:53 PM
Unexpected close reading NET message => aborting.
This is usually a terminating process on the client (srvustxigppvm2). Upgrading the client to the same version running on the Cell Manager is a good start while Data Protector A.08.00 is not considered a stable release. Going forward to A.09.07 would be best.
Regards,
Sebastian Koehler
Faulting application name: bma.exe, version: 9.0.109.0, time stamp: 0x5776e38c
Faulting module name: bma.exe, version: 9.0.109.0, time stamp: 0x5776e38c
Exception code: 0xc0000005
Fault offset: 0x000000000016b70c
Faulting process id: 0xfb8
Faulting application start time: 0x01d1dbacc7846a5b
Faulting application path: C:\Program Files\OmniBack\bin\bma.exe
Faulting module path: C:\Program Files\OmniBack\bin\bma.exe
Report Id: 5402d1f4-47a0-11e6-80c7-0090fa8a267c
Faulting package full name
I have opened a support ticket, but still waiting on an answer. Issue started with version 9.05 on July 1st. I have updated to latest/greatest July 2016 9.07 patches.
CM is 2012 R2 Std. VM on 2012 R2 DataCenter host. Job messages are logging Major [61:3003] Lost connection... -- Ipc subsystem reports: "IPC Read Error -- System error: [10054] Connection reset by peer
10 GbE fiber connections to VM, Media Agent host servers and Cisco 3850 switches.
Anyone else seeing this issue too?
hansis wrote:This command is available on non-Windows systems with the Data Protector User Interface component installed.
The documentation is very clear. The omniusers command does not exist on Windows clients, regardless if the User Interface is installed or not. If you don't mind you could use a Linux or UNIX client (with the installed User Interface) to manage the users. Just make sure the user on the remote client exists in the UserList and has the admin rights.
Regards,
Sebastian Koehler
I'm not aware of the issue. Please share the full session report with us.
Regards,
Sebastian Koehler
Hi,
I have no idea what is the reason in your case. In my case I faced the same issue and I solved it by follwing this post. Specifically by OB2_DNSTIMEOUT variable to 1.
Regards
tech88kur
Determining how to configure the Microsoft Change Log Journal size can be confusing.
The default CLP size is 512MB, which holds about 400,000 file changes.
The change journal can be tuned if you know how many files are likely to change between backups.
The following URL explains the procedure in a simple way and includes a table of possible CLP sizes and how many file changes they would cover:
http://faq.attix5.com/index.php?View=entry&EntryID=24
This article references the Microsoft utility "fsutil" to manipulte the CLP. Data Protector includes a utility (omnicjutil)
that will accomplish the same functions as fsutil from a CLP prespective. Specifics regarding omnicjutil can be found in the Data Protector user documentation, and the utility has a usage feature.
Usage synopsis:
omnicjutil -help
omnicjutil -version
omnicjutil -file file
omnicjutil -host host -volume vol [ -start [ -maxsize max -delta del ] | -stop [-wait] | -query ]
Hello nigil,
Sorry for my late reply...
None of the 2 actions solved my problem
I see on the "cell_info" that there is "-vmwaregre_agentpatch A.09.06" and "-vmwaregre_agentpatch A.09.00" on my cell manager
I just tried to remove the "-vmwaregre_agentpatch A.09.06" and not the "-vmwaregre_agentpatch A.09.00"
There is something wrong with the setup. Its not proper.
"-vmwaregre_agentpatch A.09.00" must not be seen in the cell_info file. All component version should be 906.
You can remove the "-vmwaregre_agentpatch A.09.00" and try.
Or try upgrading the clients again and see all components are upgraded to latest patch and no duplicate entries for same component.
My bad, the CM line on cell_info is this one
-host "XXXX" -os "microsoft amd64 wNT-6.1-S" -encryption 1 -cs A.09.00 -da A.09.00 -ma A.09.00 -cc A.09.00 -vepa A.09.00 -autodr A.09.00 -vmwaregre_agent A.09.00 -docs A.09.00 -pegasus A.09.00 -ts_core A.09.00 -ts_cs A.09.00 -ts_as A.09.00 -ws A.09.00 -ts_jre A.09.00 -jce_dispatcher A.09.00 -jce_serviceregistry A.09.00 -dapatch A.09.06 -mapatch A.09.06 -ccpatch A.09.06 -vepapatch A.09.06 -autodrpatch A.09.06 -vmwaregre_agentpatch A.09.06 -pegasuspatch A.09.06 -docspatch A.09.06 -ts_corepatch A.09.06 -ts_cspatch A.09.06 -ts_aspatch A.09.06 -wspatch A.09.06 -ts_jrepatch A.09.06 -jce_dispatcherpatch A.09.06 -jce_serviceregistrypatch A.09.06 -cspatch A.09.06
Another question:
Does anyone has a script (vbs or powershell) that can read the users-file to list all users? Maybe a script is available to add new users?
I can help to develop or add features and upload it to forum.
rg
hansi
Hi Hansi,
Workflow Status: closed-no change means nothing will happen unless you involve your sales contact to force product management to do something. Is the workaround with a Linux/UNIX client applicable to you?
If you develop a script, remember the entries in UserList are case sensitive. If the client is Windows it will be uppercase). If the client is UNIX it will be lowercase.
Regards,
Sebastian Koehler
Hi Sebastian, Thank you so much for the explanation...
Hi Alex,
VMware GRE and using ECC (-encryption 1) will most likely cause trouble. Since this the VMware GRE agent is also the Cell Manager the configuration with ECC exceptions will be a bit more complicated. Are you able to disable in the whole cell (and then on the Cell Manager) to see if this helps?
Regards,
Sebastian Koehler
It would be great if you could mark this topic as resolved, if I was able to answer your questions.
Regards,
Sebastian Koehler
Hello,
No sorry, I can't disable ECC on the infrastructure, it's used by a critical server
Yes, this is correct. You can check the content of the CSV file (any editor or Excel) if you want to make sure it contains keys for all cartridges.
If that's all for the moment, please close this topic and thanks for all the Kudos. :)
Regards,
Sebastian Koehler
Hi Don,
you can shut down Data Protector (omnisv stop) and delete the content of programdata\omniback\tmp\appserver. Starting the services again (omnisv start) will re-deploy the AppServer and bring a few files back (200-400MB). What Data Protector release are you running (omnisv -version)?
Don't delete the AppServer folder itself, since it is not re-created on older versions of Data Protector!
Regards,
Sebastian Koehler