This post is more than 5 years old
63 Posts
2
10013
How to see if Direct Save works
Hi all,
We have currently a NetWorker 7.6SP3 server environment, with a DataDomain DD880 running DDOS 5.1.
We are now trying to do a client direct save from our Lotus Notes (8.5) server, with a Networker client 7.6SP3 and NMDA1.2, to our DataDomain.
How do I see if the client is sending its data directly to the DataDomain and not via storage nodes/backup server?
In the NMC I see that it using a DataDomain device which is mounted on the backup server.
In the NMDA log, I see the following:
nsrdasv: RPC Authentication: Client successfully obtained AUTH_LGTO credentials
nsrdasv: Default DFA handling for client is 'Fallback'
nsrdasv: ssid 636581143 using direct save to `bvault40'
nsrdasv: Successfully setup direct saves
(bvault40 is the backup server)
So it seems direct save is successful, but it's doing a direct save to the backup server, not to the datadomain. Or am I wrong?
When I check the transferred bytes over the backup interface of the backup server, I see that a lot of data is sent over this interface.
And currently there is no other backup running than this notes backup.
Kind regards
CarlosRojas
1.7K Posts
0
July 3rd, 2012 00:00
Hi,
I actually think you are missing 2 variables:
NSR_DEVICE_INTERFACE=DATA_DOMAIN
Specifies whether the backup should always be stored on the Data Domain device from the given pool.
Optional for manual deduplication backups with the Data Domain media type only. Set this parameter when
the backup pool contains a mixture of Data Domain devices and other types of devices, for example, AFTD,
tape, and so on.
Do not set for a scheduled deduplication backup. For a scheduled deduplication backup, ensure that the Data
Domain Backup attribute is set in the NMDA Client resource when the pool has mixed devices.
• By default, backup data is stored on the most appropriate device from a given pool, as determined by NetWorker.
• DATA_DOMAIN = Backup data is always stored on the Data Domain device.
and
NSR_DIRECT_ACCESS
Specifies the method used to perform a deduplication backup to a NetWorker Data Domain device.
• Default (default) = Data Domain backup attempts to use the client direct method that deduplicates data
in the NMDA host and sends unique blocks directly to the Data Domain device. If the client direct method cannot be used, the backup is deduplicated on the storage node.
• No = The client direct method is not attempted. The Data Domain backup is deduplicated on the storage
node or the Data Domain device.
• Yes = Data Domain backup uses only the client direct method. If this method cannot be used, the backup fails.
So using both variables should work as expected, Lotus client using Data Domain devices with DFA.
Thank you.
Carlos.
CarlosRojas
1.7K Posts
1
July 3rd, 2012 00:00
Hi,
Have you configured the client accordingly to documentation? Looks to me as if the client is not using DFA.
For Lotus backups:
If you back up 32-bit Lotus Domino or Notes on a 64-bit Windows operating system, set the PATH parameter in the configuration file or wizard to the location of the 32-bit libDDBoost.dll library.
For example:
PATH=C:\Program Files\Legato\nsr\bin\ddboost32
Also, you need to set the following variable:
NSR_DIRECT_ACCESS=yes
• Default (default) = Data Domain backup attempts to use the client direct method that deduplicates data
on the NMDA host and sends unique blocks directly to the Data Domain device. If the client direct
method cannot be used, the backup is deduplicated on the storage node.
• No = The client direct method is not attempted. The Data Domain backup is deduplicated on the storage
node or the Data Domain device.
• Yes = Data Domain backup uses only the client direct method.
What is the configuration set on the client?
Thank you.
Carlos.
TimTh
63 Posts
0
July 3rd, 2012 00:00
Hello Carlos,
Thank you for your reply.
I've created the client using the "new client" wizzard in NMC.
It's a 64bit domino running on a 64bit Windows.
Here is the backup configuration (generated by the wizzard):
NSR_BACKUP_ALL_EXTENSIONS:"TRUE";
NSR_BACKUP_LEVEL:"full";
NSR_BACKUP_LOTUS_DIR:"TRUE";
NSR_CROSS_MOUNT_POINTS:"TRUE";
NSR_DEBUG_LEVEL:"3";
NSR_DIAGNOSTIC_DEST:"I\:\\legato_logs";
NSR_DPRINTF:"TRUE";
NSR_FOLLOW_LINKS:"TRUE";
NSR_LOTUS_DATA_DIR:"G\:\\EMEAARC01";
NSR_NOTES_INI_PATH:"G\:\\EMEAARC01\\notes.ini";
NSR_PARALLELISM:"8";
NSR_SKIPDBERRORS:"TRUE";
NSR_WIZARD_VERSION:"W1.1";
NSR_XBSA_DEBUG:"TRUE";
Notes_ExecDirectory:"C\:\\Lotus\\Domino";
PATH:"\"G\:\\EMEAARC01\;H\:\\EMEAARC01\;I\:\\EMEAARC01\;J\:\\EMEAARC01\;C\:\\Lotus\\Domino\;C\:\\Program Files\\Legato\\nsr\\bin\"";
name:"Lotus";
type:"LotusCFG";
So it seems that NSR_DIRECT_ACCESS isn't set, so it will use the default. And thus tries to do a direct save.
I've also logged on to the notes server, and searched for the libDDBoost.dll (64-bit in my case), which is located in C:\Program Files\Legato\nsr\bin\libDDBoost.dll.
And as you can see, C:\Program Files\Legato\nsr\bin is included in the PATH variable.
Kind regards
TimTh
63 Posts
0
July 3rd, 2012 04:00
Hello Carlos,
I'm going to let my full backup finish, and then I'm going to add these parameters and give it a new try.
I'll keep you informed.
Kind regards
Tim
TimTh
63 Posts
0
July 3rd, 2012 22:00
Seems it's getting better.
It did gave me the error "Since checkpoint restart is enabled, NSR_DIRECT_ACCESS can not be set to 'Yes'. Please set it to 'default' or 'No', or disable checkpoint restart."
However, I rather have the direct access than the checkpoint restart, so I disabled the checkpoint restart.
In the debugs, I get a lot more information telling me that it's trying to do a direct access.
However, it still fails.
nsrdasv: RPC Authentication: Client successfully obtained RPCSEC_GSS credentials
nsrdasv: Default DFA handling for client is 'Fallback'
nsrdasv: Device attribute block size is 262144
nsrdasv: Loading library at libDDBoost.dll
nsrdasv: Getting function address for ddp_errstr...nsrdasv: 80002ea6
nsrdasv: Getting function address for ddp_get_version...nsrdasv: 8000342c
nsrdasv: Getting function address for ddp_init...nsrdasv: 80002f0a
nsrdasv: Getting function address for ddp_shutdown...nsrdasv: 8000326e
nsrdasv: Getting function address for ddp_instance_create...nsrdasv: 80003542
nsrdasv: ddcl_version 2.4.1.0
nsrdasv: Getting function address for ddp_instance_destroy...nsrdasv: 80003e1c
nsrdasv: Getting function address for ddp_log_init...nsrdasv: 800042f2
nsrdasv: Getting function address for ddp_event_init...nsrdasv: 800045d4
nsrdasv: Getting function address for ddp_exception_init...nsrdasv: 800048da
nsrdasv: Getting function address for ddp_connect...nsrdasv: 80004ac4
nsrdasv: Getting function address for ddp_connect_with_user_pwd...nsrdasv: 8000533c
nsrdasv: Getting function address for ddp_disconnect...nsrdasv: 80005a88
nsrdasv: Getting function address for ddp_comp_stat...nsrdasv: 8000d39a
nsrdasv: Getting function address for ddp_get_storage_units_list...nsrdasv: 80006484
nsrdasv: Getting function address for ddp_get_stream_counts...nsrdasv: 8000692a
nsrdasv: Getting function address for ddp_get_system_info...nsrdasv: 80006cea
nsrdasv: Getting function address for ddp_create_storage_unit...nsrdasv: 80005f42
nsrdasv: Getting function address for ddp_delete_storage_unit...nsrdasv: 800061e2
nsrdasv: Getting function address for ddp_open_file...nsrdasv: 800072da
nsrdasv: Getting function address for ddp_close_file...nsrdasv: 80007c92
nsrdasv: Getting function address for ddp_read...nsrdasv: 80007fc6
nsrdasv: Getting function address for ddp_write...nsrdasv: 8000843c
nsrdasv: Getting function address for ddp_access...nsrdasv: 800088dc
nsrdasv: Getting function address for ddp_utime...nsrdasv: 8000b2b0
nsrdasv: Getting function address for ddp_fchmod...nsrdasv: 80008d6a
nsrdasv: Getting function address for ddp_fstat...nsrdasv: 80009028
nsrdasv: Getting function address for ddp_stat...nsrdasv: 800092d4
nsrdasv: Getting function address for ddp_statfs...nsrdasv: 800097e4
nsrdasv: Getting function address for ddp_fsync...nsrdasv: 80009b74
nsrdasv: Getting function address for ddp_ftruncate...nsrdasv: 80009dec
nsrdasv: Getting function address for ddp_unlink...nsrdasv: 8000ad7c
nsrdasv: Getting function address for ddp_rename...nsrdasv: 8000a0fe
nsrdasv: Getting function address for ddp_link...nsrdasv: 8000a802
nsrdasv: Getting function address for ddp_mkdir...nsrdasv: 8000b746
nsrdasv: Getting function address for ddp_rmdir...nsrdasv: 8000bb96
nsrdasv: Getting function address for ddp_close_dir...nsrdasv: 8000c69e
nsrdasv: Getting function address for ddp_open_dir...nsrdasv: 8000bfb6
nsrdasv: Getting function address for ddp_readdir...nsrdasv: 8000ca14
nsrdasv: Getting function address for ddp_rewinddir...nsrdasv: 8000cd18
nsrdasv: Getting function address for ddp_telldir...nsrdasv: 8000cef2
nsrdasv: Getting function address for ddp_seekdir...nsrdasv: 8000d130
nsrdasv: Getting function address for ddp_filecopy_start...nsrdasv: 8000d5ec
nsrdasv: Getting function address for ddp_filecopy_stop...nsrdasv: 8000d9b6
nsrdasv: Getting function address for ddp_filecopy_status...nsrdasv: 8000dc12
nsrdasv: ddcl_init returned success
nsrdasv: ddcl_connect failed with DDR ddr02nb on mount point /backup/ost with error Connecting to 'ddr02nb' failed ([5040] calling system(), returns nonzero).
nsrdasv: active file 2213794012 recreated by mmd
Guess it had something to do with a network issue, credentials or some kind of access.
I'm looking into it. And keep you updated.
Kind regards
TimTh
63 Posts
1
July 3rd, 2012 22:00
The DataDomain ddr02nb wasn't in the hostsfile of the client.
Now the direct save is working.
Thanks!