cancel
Showing results for 
Search instead for 
Did you mean: 

Error en backup de Exchange. Unable to initialize nbfsd

Guillenet
Level 3

El registro que obtengo es este

10/10/2018 4:49:17 PM - Información nbjm (pid = 6128) iniciando la tarea de copia de seguridad (jobid = 47391) para el cliente CSWVEXMBX2.XXXX.LOCAL, política Test_VIPS, calendario complete
02/10/2018 4:49:18 PM - estimado 11141838 Kbytes necesarios
02/10/2018 4:49:18 PM - Información nbjm (pid = 6128) trabajo de copia de seguridad de datos (backupid = dag1_1538509757) para el cliente CSWVEXMBX2.XXXX.LOCAL , política Test_VIPS, programa completo en la unidad de almacenamiento stu -bdisk-D2DexchGRT 2/2/2018
4:49:18 PM - proceso iniciado bpbrm (6800)
10/2/2018 4:49:25 PM - Info bpbrm (pid = 6800) CSWVEXMBX2.XXXX.LOCAL es el host para datos de copia de seguridad del
2/10/2018 4:49:25 PM - Info bpbrm (pid = 6800) leyendo la lista de archivos del cliente
10/2/2018 4:49:26 PM - conectando el
10/2/2018 4:49:29 PM - Info bpbrm (pid = 6800) iniciando bpbkar32 en el cliente
10/10/2018 4:49:29 PM - conectado hora de conexión: 00:00:03
10/2/2018 4:49:37 PM - Información bpbkar32 (pid = 7292) Copia de seguridad iniciada
10/2/2018 4:49:37 PM - Información bptm (pid = 6772) inicio
10 / 2/2018 4:49:38 PM - Información bptm (pid = 6772) usando 262144 tamaño del archivo de datos
10/2/2018 4:49:38 PM - Información bptm (pid = 6772) configurando recibir el búfer de la red a 1049600 bytes
10 / 2/2018 4:49:38 PM - Información bptm (pid = 6772) usando 30 buffers de datos
10/2/2018 4:49:39 PM - Información bptm (pid = 6772 ) iniciar copia de seguridad
2/10/2018 4: 49:39 PM - Información bpbkar32 (pid = 7292) INF - en espera de montaje mutex
10/2/2018 4:49:40 PM - Información bptm (pid = 6772) El proceso secundario de copia de seguridad es pid 5324.8228
10/2/2018 4: 49:40 PM - Info bptm (pid = 5324) comienza el
2/2/2018 4:49:40 PM - comienza a escribir
2/10/2018 4:50: 53 PM - Error bpbrm (pid = 6800) del cliente dag1: ERR - No se pudo inicializar nbfsd.
02/10/2018 4:54:51 PM - Información bpbrm (pid = 6800) DB_BACKUP_STATUS es 0
10/2/2018 4:54:54 PM - Error bpbrm (pid = 6800) del cliente dag1: ERR - Se encuentra un Error mientras intenta obtener archivos adicionales para el Almacén de información de Microsoft: \ VIPS \ Logs_1538509720 \
10/10/2018 4:54:54 PM - Error bpbrm (pid = 6800) del cliente dag1: ERR - La restauración granular de Exchange desde esta imagen no puede funcionar.
10/2/2018 4:54:54 PM - Info bptm (pid = 6772) esperó el búfer completo 2 veces, retrasado 5012 veces
10/2/2018 4:54:54 PM - Info bptm (pid = 6772) SALIENDO con estado 0 <----------
10/2/2018 4:54:54 PM - Info bpbrm (pid = 6800) validando imagen para el cliente dag1
2/10/2018 4:54:57 PM - termina la escritura; tiempo de escritura: 00:05:17
la operación solicitada fue parcialmente exitosa (1)

El trabajo se completó con éxito, pero algunos archivos pueden haber estado
ocupados o inaccesibles. Consulte el informe de problemas o los registros del cliente para obtener más detalles.

Utilice Netbackup 7.5 que funcionó en Windows Server 2008 R2.

Y Exchange 2010 también se realizó en Windows Server 2008 R2.
12 REPLIES 12

Lowell_Palecek
Level 6
Employee

Have you enabled NFS as described in the NetBackup for Exchange admin guide?

If I followed the entire guide.
Up to a week ago everything worked correctly.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please double-check NFS settings on all DAG members. 
Something has changed on one or more nodes. 

I keep finding the same problem.
I tried to follow this link:
https://www.veritas.com/support/en_US/article.100000686

But I receive error exit status = 25 on the client.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Can you please show us the commands and output on both the media server and client CSWVEXMBX2

On the netbackup server:

C:\Program Files\Veritas\Netbackup\bin> nbfsd -d -v 5 -j 1 -B dag1_1

PORT=7394

CRED1=768B5115F3FD4A4A13DEAEB171E9D378DCE9795E79EB59F1EF50FBA2AA4CABCED0E90DE1699ADD1114B6E3C40EAF1CC16114446E0DA40E1D6A1F3CA75F034AF8

CRED2=A7798C27B662437EFA47D4A57220AD8F4A180015F481175D2A3FFD65A8189017CAA6388E9F267BC3C0C41C367281CA9D8C765EC96BD90A41D6445EF3C44CFA63

NBFSD STARTED 0

On the client:

C:\Program Files\Veritas\Netbackup\bin> nbfs mount -server cswbkp.XXXX.local -cred 768B5115F3FD4A4A13DEAEB171E9D378DCE9795E79EB59F1EF50FBA2AA4CABCED0E90DE1699ADD1114B6E3C40EAF1CC16114446E0DA40E1D6A1F3CA75F034AF8 *

connect to cswbkp.xxxx.local failed

EXIT_STATUS=25

The log in the client:

10:03:15.094 [6304.404] <2> rpc_connect: connecting to cswbkp.XXXX.local

10:03:36.123 [6304.404] <16> rpc_connect: can't create TCP connection to cswbkp.XXXX.local (12 10060), will retry...

10:03:41.131 [6304.404] <2> rpc_connect: connecting to cswbkp.XXXX.local

10:04:02.175 [6304.404] <16> rpc_connect: can't create TCP connection to cswbkp.XXXX.local (12 10060), will retry...

10:04:07.183 [6304.404] <2> rpc_connect: connecting to cswbkp.XXXX.local

10:04:28.196 [6304.404] <16> rpc_connect: can't create TCP connection to cswbkp.XXXX.local (12 10060), giving up

Ping client to server:

Z:\>ping cswbkp.XXXX.local

Pinging cswbkp.XXXX.local [192.168.X.XXX] with 32 bytes of data:

Reply from 192.168.X.XXX: bytes=32 time<1ms TTL=128

Reply from 192.168.X.XXX: bytes=32 time<1ms TTL=128

Reply from 192.168.X.XXX: bytes=32 time<1ms TTL=128

Reply from 192.168.X.XXX: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.X.XXX:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Telnet to 7394 is OK!

Firewall is down!

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
@Guillenet wrote:

Telnet to 7394 is OK!

@Guillenet wrote:

Firewall is down!


Interesting.... 

Alexis_Jeldrez
Level 6
Partner    VIP    Accredited Certified

@Guillenet

Have you tried enabling the firewall and then making specific TCP rules for NetBackup?

Also, double-check the NFS server installation. If you are really stuck, just redo the whole Exchange GRT implementation, might be faster than troubleshooting it. It would be a pity, though, since you've already detected the cause of the problem.

The firewall is already enabled and enable all ports used by NFS. (They were already open). Check again the client service for NFS and it is running ok.

Alexis_Jeldrez
Level 6
Partner    VIP    Accredited Certified

Are you still getting status 25 when trying the procedure in https://www.veritas.com/support/en_US/article.100000686 ?

PD: You can keep doing regular Information Store backups without GRT, in the meantime.

I still get status 25 on the nbfsd test.
The backup of the complete database is completed correctly.