Data Protector Cannot connect to the SCM (Service Control Manager)
Antigamente meus backups de BD (Banco de Dados) se resumiam a cópias em disco que iam para HDs externos e tal. Há quase 6 meses eu venho trabalhando com uma ferramenta de backup de verdade, com biblioteca de fitas LTO, robô de mudança de fitas e toda aquela parafernália que faz com que o tempo de recuperação de um backup caia de 7 horas para 3 (ou até menos). Afinal, quando o BD para ninguém quer saber como você vai fazer para recuperá-lo, apenas querem que o faça o mais rápido possível. Bastante razoável.
Essa ferramenta (HP Data Protector 6.20) consiste basicamente em um Servidor (Cell Manager) que conversa com o Cliente (local onde estão os dados que será feito backup ou onde você deseja restaurar o backup). Cada Servidor pode também ser um "Installation Server", ou seja, conter os aplicativos de instalação, evitando que toda vez que você precisar adicionar um novo cliente, ter que ir lá ao mesmo, fisicamente, com um DVD na mão e um manual embaixo do braço para fazer a dita instalação.
Estranhamente na instalação de um desses clientes, Windows 2008 R2, um erro estava ocorrendo:
[Normal] Starting installation session...
[Normal] Getting list of clients for installation...
[Normal] Done.
[Normal] Expanding and checking clients to be installed...
[Normal] Connecting to client umundok.dominio.local...
[Normal] Valid username and password must be specified...
[nesse momento o infiel me pedia um domínio, usuário e senha. Eu colocava o usuário e senha com permissões administrativas]
[Normal] Connecting to client umundok.dominio.local...
[Normal] Done.
[Normal] Installing the Data Protector bootstrap service on client umundok.dominio.local...
[Critical] [110:1022] Cannot connect to the SCM (Service Control Manager) on client umundok.dominio.local:
[5] Access is denied.
[Normal] Installation session finished with errors!
O usuário estava cadastrado no AD. Tanto o Cell Manager como o cliente estavam no mesmo domínio e ambos se enxergavam, enamorados como um casal feliz e em harmonia. Então o que estava errado? Quem impedia o feliz encontro dos dois?
Recordando minhas memórias do curso de Data Protector, lembrei-me de uma questão relacionada a permissões entre cliente/servidor. Consultei a apostila do curso e descobri o seguinte:
É necessário adicionar um Usuário com direitos administrativos ao serviço do INET. Para isso abra o Prompt de Comando como administrador e execute o seguinte comando para verificar se já existe tal usuário:
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -list
Para adicionar um novo usuário ao serviço, faça uso do seguinte comando (lembrando que esse usuário precisa estar já criado no AD):
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -add [domain]\[ad_user]
Please enter password:**********
Please retype password:**********
User '[domain]\[ad_user]' was successfully added.
Por fim basta executar o próximo comando para que o Installation Server possa usufruir da conta criada acima:
omniinetpasswd.exe -inst_srv_user [domain]\[ad_user]
User '[domain]\[ad_user]' is configured to be used by Installation Server.
Após isso pode tentar novamente a instalação do Client que deverá funcionar e ser concluída com sucesso!
There was a time when my Database backups were just an image on an external HD e so. It's already almost six months that I have been working with a real backup tool, with LTO libraries, robotic media exchanger and all those cool things which make the recovery of a backup from 7 to 3 hours long (or even less). At least, when a database stops nobody wants to know how you gonna do to recover it. They just want you to recover as fast as you can. Very reasonable.
This tool (HP Data Protector 6.20) is basically a Client/Server architecture, where the Client (site where are the data to be saved or where you want to recover some data) and a Server (Cell Manager) which talks with this Client. Each Server also can be an "Installation Server", that means that it can have all the install files, avoiding you to, every time that you need to install a new Client, need to go there, physically, carrying out some DVD and a manual to proceed the installation.
Strange that at the installation of one of my clients, Windows 2008 R2, I was getting an error:
[Normal] Starting installation session...
[Normal] Getting list of clients for installation...
[Normal] Done.
[Normal] Expanding and checking clients to be installed...
[Normal] Connecting to client umundok.dominio.local...
[Normal] Valid username and password must be specified...
[at this point the system asked me for an User, Password and Domain to proceed. I filled with a user with admin privileges]
[Normal] Connecting to client umundok.dominio.local...
[Normal] Done.
[Normal] Installing the Data Protector bootstrap service on client umundok.dominio.local...
[Critical] [110:1022] Cannot connect to the SCM (Service Control Manager) on client umundok.dominio.local:
[5] Access is denied.
[Normal] Installation session finished with errors!
The user was already a member of the Windows AD. As the Cell Manager as the Client were on the same domain and both were reaching each other, as a happy couple in harmony. So what was wrong? What was avoiding the happy meeting of both?
Remembering my Data Protector classes I found an issue related to permissions between Client/Server. I looked up my classes notes and found something that could be the solution to the problem:
It's necessary to add a user with admin rights to the INET service. To do this open the Command Prompt as administrator and execute this command to list if there's already some user there:
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -list
To add a new user there, execute the command (remember that this user must exist on the AD):
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -add [domain]\[ad_user]
Please enter password:**********
Please retype password:**********
User '[domain]\[ad_user]' was successfully added.
To finish execute this command to make with the Installation Server use the account added:
omniinetpasswd.exe -inst_srv_user\
User '[domain]\[ad_user]' is configured to be used by Installation Server.
And then you can try again the client installation, which might work fine this time!
Essa ferramenta (HP Data Protector 6.20) consiste basicamente em um Servidor (Cell Manager) que conversa com o Cliente (local onde estão os dados que será feito backup ou onde você deseja restaurar o backup). Cada Servidor pode também ser um "Installation Server", ou seja, conter os aplicativos de instalação, evitando que toda vez que você precisar adicionar um novo cliente, ter que ir lá ao mesmo, fisicamente, com um DVD na mão e um manual embaixo do braço para fazer a dita instalação.
Estranhamente na instalação de um desses clientes, Windows 2008 R2, um erro estava ocorrendo:
[Normal] Starting installation session...
[Normal] Getting list of clients for installation...
[Normal] Done.
[Normal] Expanding and checking clients to be installed...
[Normal] Connecting to client umundok.dominio.local...
[Normal] Valid username and password must be specified...
[nesse momento o infiel me pedia um domínio, usuário e senha. Eu colocava o usuário e senha com permissões administrativas]
[Normal] Connecting to client umundok.dominio.local...
[Normal] Done.
[Normal] Installing the Data Protector bootstrap service on client umundok.dominio.local...
[Critical] [110:1022] Cannot connect to the SCM (Service Control Manager) on client umundok.dominio.local:
[5] Access is denied.
[Normal] Installation session finished with errors!
O usuário estava cadastrado no AD. Tanto o Cell Manager como o cliente estavam no mesmo domínio e ambos se enxergavam, enamorados como um casal feliz e em harmonia. Então o que estava errado? Quem impedia o feliz encontro dos dois?
Recordando minhas memórias do curso de Data Protector, lembrei-me de uma questão relacionada a permissões entre cliente/servidor. Consultei a apostila do curso e descobri o seguinte:
É necessário adicionar um Usuário com direitos administrativos ao serviço do INET. Para isso abra o Prompt de Comando como administrador e execute o seguinte comando para verificar se já existe tal usuário:
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -list
Para adicionar um novo usuário ao serviço, faça uso do seguinte comando (lembrando que esse usuário precisa estar já criado no AD):
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -add [domain]\[ad_user]
Please enter password:**********
Please retype password:**********
User '[domain]\[ad_user]' was successfully added.
Por fim basta executar o próximo comando para que o Installation Server possa usufruir da conta criada acima:
omniinetpasswd.exe -inst_srv_user [domain]\[ad_user]
User '[domain]\[ad_user]' is configured to be used by Installation Server.
Após isso pode tentar novamente a instalação do Client que deverá funcionar e ser concluída com sucesso!
There was a time when my Database backups were just an image on an external HD e so. It's already almost six months that I have been working with a real backup tool, with LTO libraries, robotic media exchanger and all those cool things which make the recovery of a backup from 7 to 3 hours long (or even less). At least, when a database stops nobody wants to know how you gonna do to recover it. They just want you to recover as fast as you can. Very reasonable.
This tool (HP Data Protector 6.20) is basically a Client/Server architecture, where the Client (site where are the data to be saved or where you want to recover some data) and a Server (Cell Manager) which talks with this Client. Each Server also can be an "Installation Server", that means that it can have all the install files, avoiding you to, every time that you need to install a new Client, need to go there, physically, carrying out some DVD and a manual to proceed the installation.
Strange that at the installation of one of my clients, Windows 2008 R2, I was getting an error:
[Normal] Starting installation session...
[Normal] Getting list of clients for installation...
[Normal] Done.
[Normal] Expanding and checking clients to be installed...
[Normal] Connecting to client umundok.dominio.local...
[Normal] Valid username and password must be specified...
[at this point the system asked me for an User, Password and Domain to proceed. I filled with a user with admin privileges]
[Normal] Connecting to client umundok.dominio.local...
[Normal] Done.
[Normal] Installing the Data Protector bootstrap service on client umundok.dominio.local...
[Critical] [110:1022] Cannot connect to the SCM (Service Control Manager) on client umundok.dominio.local:
[5] Access is denied.
[Normal] Installation session finished with errors!
The user was already a member of the Windows AD. As the Cell Manager as the Client were on the same domain and both were reaching each other, as a happy couple in harmony. So what was wrong? What was avoiding the happy meeting of both?
Remembering my Data Protector classes I found an issue related to permissions between Client/Server. I looked up my classes notes and found something that could be the solution to the problem:
It's necessary to add a user with admin rights to the INET service. To do this open the Command Prompt as administrator and execute this command to list if there's already some user there:
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -list
To add a new user there, execute the command (remember that this user must exist on the AD):
C:\Program Files\OmniBack\bin>omniinetpasswd.exe -add [domain]\[ad_user]
Please enter password:**********
Please retype password:**********
User '[domain]\[ad_user]' was successfully added.
To finish execute this command to make with the Installation Server use the account added:
omniinetpasswd.exe -inst_srv_user
User '[domain]\[ad_user]' is configured to be used by Installation Server.
And then you can try again the client installation, which might work fine this time!
So basically this is a way of installing a backup system for data so if you lose one storage place you have another, right? It''s hard to tell, it seems so technical. Maybe if I read it a few times it will male sense.
ResponderExcluirI'm not preparing for the Armageddon, I'm preparing for the inevitable onslaught of fresh produce that comes for about two months a year up here, three months if we're lucky, with additional gluts of things like strawberries and asparagus in the spring.
Yes, or you can even restore in the same place, if the problem was only on data lose... Don't worry in trying understand it. I still don't some time!
ExcluirAspargus are nice...
Yes, or you can even restore in the same place, if the problem was only on data lose... Don't worry in trying understand it. I still don't some time!
ExcluirAspargus are nice...
Yes, or you can even restore in the same place, if the problem was only on data lose... Don't worry in trying understand it. I still don't some time!
ResponderExcluirAspargus are nice...
It's called a receipt, and I highly recommend you always get one!Here unless I'm buying something small like vegetables from someone I really know well I always ask for one. The rules are probably different where you are but if you paid with a credit card or a check or a bank transfer there might be some kind of record of the payment being made at your bank or you credit card company, good luck.
ResponderExcluirExcelente explicação!
ResponderExcluirTô tendo que me virar com o Data Protector sem nunca ter feito curso, daí de vez em quando tropeço em problemas assim. Salvou o meu dia, obrigado! :)
SHOW!
ResponderExcluir