NDMP fails

FAS3020 is not a part of the command.

When the backup group is running, NAS box changes mover state to Active & data state to Connected and then in a few seconds back to idle.

I hope that NetApp FAS3020c is not part of backup command. If not can you check ndmpd log on filer?

Can you show ndmpd log?

I have some outputs but we are trying to figure out with NetApp how to activate the actual NDMP logs -

GGNUFILER01> ndmpd status
ndmpd ON.
Session: 95
Active
version: 4
Operating on behalf of primary host.
tape device: nrst1m
mover state: Idle
data state: Idle
data operation: None
GGNUFILER01> ndmpd status
ndmpd ON.
Session: 97
Active
version: 4
Operating on behalf of primary host.
tape device: not open
mover state: Idle
data state: Idle
data operation: None
Session: 96
Active
version: 4
Operating on behalf of primary host.
tape device: nrst1m
mover state: Idle
data state: Idle
data operation: None
GGNUFILER01> ndmpd status
ndmpd ON.
Session: 98
Active
version: 4
Operating on behalf of primary host.
tape device: not open
mover state: Idle
data state: Idle
data operation: None
Session: 97
Active
version: 4
Operating on behalf of primary host.
tape device: not open
mover state: Idle
data state: Idle
data operation: None
GGNUFILER01> ndmpd status
ndmpd ON.
Session: 98
Active
version: 4
Operating on behalf of primary host.
tape device: nrst1m
mover state: Halted
data state: Halted
data operation: None
GGNUFILER01> ndmpd status
ndmpd ON.
Session: 103
Active
version: 4
Operating on behalf of primary host.
tape device: not open
mover state: Idle
data state: Idle
data operation: None
Session: 102
Active
version: 4
Operating on behalf of primary host.
tape device: nrst1m
mover state: Active
data state: Connected
data operation: None
GGNUFILER01> ndmpd status
ndmpd ON.
Session: 106
Active
version: 4
Operating on behalf of primary host.
tape device: not open
mover state: Idle
data state: Idle
data operation: None
Session: 105
Active
version: 4
Operating on behalf of primary host.
tape device: not open
mover state: Idle
data state: Idle
data operation: None
Session: 102
Active
version: 4
Operating on behalf of primary host.
tape device: not open
mover state: Idle
data state: Idle
data operation: None
GGNUFILER01> mt -t nrst0m status
Tape drive: COMPAQ SuperDLT1
Status: in use
Format: 133Kbpi 200 GB cmp SDLT1
fileno = 4 blockno = 1 resid = 0
GGNUFILER01> ndmpd status
ndmpd ON.
Session: 107
Active
version: 4
Operating on behalf of primary host.
tape device: nrst0m
mover state: Idle
data state: Idle
data operation: None
Session: 111
Active
version: 4
Operating on behalf of primary host.
tape device: nrst1m
mover state: Idle
data state: Idle
data operation: None

In the meantime, can you please help. If the NAS folders are accessed from a Windows server like - \\NASserver\Test Folder, what should be the save set for the client NASserver for NDMP backups. Itried, Tes Folder, /Test Folder & \Test Folder but all gave the same error. I still want to be clear which one is the right one.

Check /etc/log. With ndmpd you can set debug level too.

I think \\NASserver\Test Folder should work as I believe this format is even mentioned somewhere in recent docs (with quotes) and you will need to probably to modify save command via backup command as that is share and not system belonging to Windows box.

I don't understand this second part, but you try it. You will find somewhere in release notes I believe note about share backups on Windows and this is where it is specified how to do it (\\ thing). However, I would rather focus on NetApp issue as key thing here is NDMP backup.

I will test this today.

I was not doing this till now on the assumption that if the client resoruce is for the NASserver (host name as client name), then Save Set should not need the client name again as \\NASserver\Test Folder.

Support has suggested using /vol. How do I find which /vol to use?

NetApp admin should tell you that. Most probably you have something like /vol/vol0

Hello,
Your backups are failing due to incorrect saveset name.
client config if incorrect also.
SAVESET should be
/vol/CIFSA_CORPLAW/QCORPLAW
i.e
vol/volname/qtree name
You can alternatively use volname only that will work, i like to create and use qtrees.(/vol/CIFSA_CORPLAW)
Where CIFSA_CORPLAW is my volume

Client config:
Application info tab following settings should be used depending on your enviroment.
HIST=y
UPDATE=y
DIRECT=y
EXTRACT_ACL=y
UTF8=y

Lastly client should be NDMP & storage node feild of client resource should be specified, this is if you use netapp as storage node

One more thing, you only need as below to backup cmd
nsrndmp_save -T dump

Thanks,

I got this checked by support but am yet to test this as library is giving some other issues.

I would get this done on Tuesday and update.

What about indexes. I have created a DR pool with save sets as INDEX: & Bootstrap.

Is it sufficient?

Also wanted to check if we need to select the group names in this pool for the groups whose indexes should go to DR pool?

saveset should be enough even I prefer savgerp -O & no index save approach.