Yes we are talking about NMM, As you requested the data follows below:
Version 7.6.1 Build 397
Command
Samehost test for host1 - BHZSM1200 and host2 - bhzsm1200.dir.svc.accenture.com, and determined to be the same machine which is BHZSM1200.dir.svc.accenture.com.
DNS cache: host: 10.20.102.106, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com host: 127.0.0.1, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com host: BHZSM1200, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com host: BHZSM1200.dir.svc.accenture.com, status: STATUS_OK, head: BHZSM1200.dir.sv c.accenture.com host: localhost, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com Clients cache: NMM .. changing backup name BHZSM1200 to primary name bhzsm1200.dir.svc.accentur e.com for multi NIC client.
List of valid saveset entries for APPLICATIONS on client bhzsm1200.dir.svc.accen ture.com ... Initializing data to display...
"APPLICATIONS:\DFS Replication service writer" "APPLICATIONS:\DFS Replication service writer\Local_Image" "APPLICATIONS:\DFS Replication service writer\MPC" "APPLICATIONS:\DFS Replication service writer\BR_ESD" 68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
Yes we are talking about NMM, As you requested the data follows below:
Version 7.6.1 Build 397
Command
Samehost test for host1 - BHZSM1200 and host2 - bhzsm1200.dir.svc.accenture.com, and determined to be the same machine which is BHZSM1200.dir.svc.accenture.com.
DNS cache: host: 10.20.102.106, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com host: 127.0.0.1, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com host: BHZSM1200, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com host: BHZSM1200.dir.svc.accenture.com, status: STATUS_OK, head: BHZSM1200.dir.sv c.accenture.com host: localhost, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com Clients cache: NMM .. changing backup name BHZSM1200 to primary name bhzsm1200.dir.svc.accentur e.com for multi NIC client.
List of valid saveset entries for APPLICATIONS on client bhzsm1200.dir.svc.accen ture.com ... Initializing data to display...
"APPLICATIONS:\DFS Replication service writer" "APPLICATIONS:\DFS Replication service writer\Local_Image" "APPLICATIONS:\DFS Replication service writer\MPC" "APPLICATIONS:\DFS Replication service writer\BR_ESD" 68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
Made the setting as posted, but still giving this error when I run the snapshot job test it when it starts to jump by 34 mb to 50% and after a few seconds it crashes. The following error message.
I don't think that is the failure, it's just you have set the "Verbose" option in the group configuration, and that is the detail of the index being saved.
Can you please render the nmm.raw file on the client (nsr_render_log nmm.raw > nmm.log) and please attach here the output.
Also please check the files /nsr/tmp/sg/group_name_folder and check out the real failure, as the output added in your previous post was not really a failure.
Thanks for the attachment, actually that one gave me the clue.
The save set you have specified are not correct, as in the save set you need to remove the quotes. This is what you have:
"APPLICATIONS:\DFS Replication service writer" "APPLICATIONS:\DFS Replication service writer\Local_Image" "APPLICATIONS:\DFS Replication service writer\MPC" "APPLICATIONS:\DFS Replication service writer\BR_ESD"
You need to set these ones, and also please remove the pool from client configuration (you have currently "snapshot" pool selected) and set the pool in the group configuration as, when it's snapshot type backup, you need to set the pool in the group configuration, just below the snapshot policy (serverless backup).
APPLICATIONS:\DFS Replication service writer APPLICATIONS:\DFS Replication service writer\Local_Image APPLICATIONS:\DFS Replication service writer\MPC APPLICATIONS:\DFS Replication service writer\BR_ESD
I can still see in the client configuration that you have a pool selected. please leave the pool in client configuration blank.
Also please note that you are probably trying to backup twice the same data. Save sets to be set are as follows:
Option 1:
APPLICATIONS:\DFS Replication service writer
Option 2:
APPLICATIONS:\DFS Replication service writer\Local_Image APPLICATIONS:\DFS Replication service writer\MPC APPLICATIONS:\DFS Replication service writer\BR_ESD
Note that save set APPLICATIONS:\DFS Replication service writer will backup all sub-components, so no need to specify all the save sets.
36115_carloscor
217 Posts
0
August 8th, 2011 07:00
Hello again,
As far as I can see I understand that you didn't set the correct backup command:
bhzsm1200: APPLICATIONS:\DFS Replication service writer\MPC (returned from savefs) skipped
Please ensure that you have the following configuration on the client, and also in the group:
Client configuration:
Save set:
Please set the DFS save set name as follows:
APPLICATIONS:\DFS Replication service writer
Backup command:
nsrsnap_vss_save
Application Information:
NSR_SNAP_TYPE=vss
Group Configuration:
Snapshots:
Snapshot box checked, as this is a Snapshot based backup.
Snapshot policy:
Serverless backup
Snapshot Pool:
Whatever pool you want to use you have to select it here, and leave the one in client configuration blank, as the pool will be defined in here
Advanced tab:
Client retries=0
Inactivity Time out=0
Savegrp paralellism=0
Please apply this configuration changes and run a new backup and please let us know the results.
Thank you.
Carlos.
36115_carloscor
217 Posts
1
August 4th, 2011 05:00
Hello Anderson,
I understand we are talking about NMM, correct? If so, could you please let us know the version and build?
Also please run the following command on the client and let us know the output:
nsrsnap_vss_save -v -?
Thank you.
Carlos.
agracci
34 Posts
0
August 4th, 2011 06:00
Hello Carlos,
Yes we are talking about NMM, As you requested the data follows below:
Version 7.6.1 Build 397
Command
Samehost test for host1 - BHZSM1200 and host2 - bhzsm1200.dir.svc.accenture.com,
and determined to be the same machine which is BHZSM1200.dir.svc.accenture.com.
DNS cache:
host: 10.20.102.106, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
host: 127.0.0.1, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
host: BHZSM1200, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
host: BHZSM1200.dir.svc.accenture.com, status: STATUS_OK, head: BHZSM1200.dir.sv
c.accenture.com
host: localhost, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
Clients cache:
NMM .. changing backup name BHZSM1200 to primary name bhzsm1200.dir.svc.accentur
e.com for multi NIC client.
List of valid saveset entries for APPLICATIONS on client bhzsm1200.dir.svc.accen
ture.com ...
Initializing data to display...
"APPLICATIONS:\DFS Replication service writer"
"APPLICATIONS:\DFS Replication service writer\Local_Image"
"APPLICATIONS:\DFS Replication service writer\MPC"
"APPLICATIONS:\DFS Replication service writer\BR_ESD"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
grateful
agracci
34 Posts
0
August 8th, 2011 07:00
Yes we are talking about NMM, As you requested the data follows below:
Version 7.6.1 Build 397
Command
Samehost test for host1 - BHZSM1200 and host2 - bhzsm1200.dir.svc.accenture.com,
and determined to be the same machine which is BHZSM1200.dir.svc.accenture.com.
DNS cache:
host: 10.20.102.106, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
host: 127.0.0.1, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
host: BHZSM1200, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
host: BHZSM1200.dir.svc.accenture.com, status: STATUS_OK, head: BHZSM1200.dir.sv
c.accenture.com
host: localhost, status: STATUS_OK, head: BHZSM1200.dir.svc.accenture.com
Clients cache:
NMM .. changing backup name BHZSM1200 to primary name bhzsm1200.dir.svc.accentur
e.com for multi NIC client.
List of valid saveset entries for APPLICATIONS on client bhzsm1200.dir.svc.accen
ture.com ...
Initializing data to display...
"APPLICATIONS:\DFS Replication service writer"
"APPLICATIONS:\DFS Replication service writer\Local_Image"
"APPLICATIONS:\DFS Replication service writer\MPC"
"APPLICATIONS:\DFS Replication service writer\BR_ESD"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
grateful
agracci
34 Posts
0
August 8th, 2011 12:00
Hello Carlos,
Made the setting as posted, but still giving this error when I run the snapshot job test it when it starts to jump by 34 mb to 50% and after a few seconds it crashes. The following error message.
bhzsm1200:index savegrp: suppressed 60 lines of output.
bhzsm1200:index mtimeasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e120000\4e1238a3.rec
bhzsm1200:index uasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e120000\
bhzsm1200:index mtimeasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e1d0000\4e1dd8c5.rec
bhzsm1200:index mtimeasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e1d0000\4e1de87c.rec
bhzsm1200:index mtimeasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e1d0000\4e1dfc75.rec
bhzsm1200:index uasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e1d0000\
bhzsm1200:index mtimeasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e1e0000\4e1ee556.rec
bhzsm1200:index uasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\4e1e0000\
bhzsm1200:index uasm -s E:\Program Files\Legato\nsr\index\bhzsm1200\db6\
bhzsm1200:index E:\Program Files\Legato\nsr\index\bhzsm1200\
bhzsm1200:index
Savegroup alert: NMM_teste completed, Total 1 Client(s), 1 Failed. Please see group completion details for more informantion.
Failed
APPLICATIONS:\DFS Replication service writer\BR_ESD Full
36115_carloscor
217 Posts
1
August 9th, 2011 00:00
Hi,
I don't think that is the failure, it's just you have set the "Verbose" option in the group configuration, and that is the detail of the index being saved.
Can you please render the nmm.raw file on the client (nsr_render_log nmm.raw > nmm.log) and please attach here the output.
Also please check the files /nsr/tmp/sg/group_name_folder and check out the real failure, as the output added in your previous post was not really a failure.
Thank you.
Carlos.
36115_carloscor
217 Posts
1
August 10th, 2011 05:00
Hi again,
Thanks for the attachment, actually that one gave me the clue.
The save set you have specified are not correct, as in the save set you need to remove the quotes. This is what you have:
"APPLICATIONS:\DFS Replication service writer"
"APPLICATIONS:\DFS Replication service writer\Local_Image"
"APPLICATIONS:\DFS Replication service writer\MPC"
"APPLICATIONS:\DFS Replication service writer\BR_ESD"
You need to set these ones, and also please remove the pool from client configuration (you have currently "snapshot" pool selected) and set the pool in the group configuration as, when it's snapshot type backup, you need to set the pool in the group configuration, just below the snapshot policy (serverless backup).
APPLICATIONS:\DFS Replication service writer
APPLICATIONS:\DFS Replication service writer\Local_Image
APPLICATIONS:\DFS Replication service writer\MPC
APPLICATIONS:\DFS Replication service writer\BR_ESD
That now should work fine.
Thank you.
Carlos.
36115_carloscor
217 Posts
0
August 10th, 2011 06:00
Hi,
I can still see in the client configuration that you have a pool selected. please leave the pool in client configuration blank.
Also please note that you are probably trying to backup twice the same data. Save sets to be set are as follows:
Option 1:
APPLICATIONS:\DFS Replication service writer
Option 2:
APPLICATIONS:\DFS Replication service writer\Local_Image
APPLICATIONS:\DFS Replication service writer\MPC
APPLICATIONS:\DFS Replication service writer\BR_ESD
Note that save set APPLICATIONS:\DFS Replication service writer will backup all sub-components, so no need to specify all the save sets.
Thanks.
Carlos.
agracci
34 Posts
0
August 10th, 2011 06:00
Carlos,
It did not work with the option you gave me, for we could schedule a webex section for you to review the settings for my environment.
Thanks,
36115_carloscor
217 Posts
0
August 10th, 2011 06:00
Hi again,
This is a forum, if you need request please open a Service Request.
What is the failure you get now?
Try to disabled the "AES Encryption" directive and run a new backup.
Also please add the following save set, which needs to be backed up together with the DFS:
SYSTEM COMPONENTS:\
Thank you.
Carlos.