Re: NDMP Exclude issue using Netbackup 8.1 and Isilon 8.1.0.4

SET EXCLUDE=Folder Space

is the correct syntax.

Maybe the directory name has more than one space character, or non-ASCII spaces:



$ ls -d1 Folder*

Folder Space

Folder Space

Folder Space

$ ls -d1 Folder* | od -c

0000000 F o l d e r S p a c e n F o

0000020 l d e r S p a c e n F o l d

0000040 e r ** S p a c e n

0000052





First example has two spaces in the middle,

second example has a space at the end.

Third example has a ‘non-breaking space’ Unicode character in the middle.

It takes two bytes in UTF-8 encoding, where

the second byte is represented by ** in the output of od -c.





While we ar at it: One more thing, big caveat, related to NDMP and include/exclude settings on Isilon:

It is possible, but dangerous, to define multiple NDMP jobs for the same base directory (FILESYSTEM)

with different include-FILES or EXCLUDE patterns.

Be warned that this will lead to unexpected results, because OneFS NDMP only keeps

one single backup timestamp per NDMP FILESYSTEM base directory and NDMP level.

FILESYSTEM=/ifs/test

FILES=a b c

FILESYSTEM=/ifs/test

FILES=d e f

Say the a b c job runs at 1am and the d e f job at 2am, the timestamp (for the given NDMP level)

for /ifs/test will finally be set to 2am.



Next day when the a b c job is running with an incremental level (>=1),

it will backup only data changes that happened after 2am (23h ago),

and miss any changes from the hour between 1am (24h ago) and 2am.



fwiw

— Peter





Related:

Re: NetApp snapshot backup

Hello guys,

I have a little problem.

I have the following environment:

– Networker Server version 18.1 (Windows 2012)

– DataDomain 6.0.x (DDBoost)

– NetApp 8.2.x (mode 7)

Problem:

I need to backup NetApp using snapshot. The shares are via NFS.

I can generate the snapshot, but during the restore I am receiving a permission error. Searched but found nothing that could help.

Some doubts:

– Is it necessary to share the volumes via CIFS as well?

– Can I use the root user for all operations? Or use the NDMP user?

Thank you very much in advance.

Related:

Re: Disaster Recovery

To answer your questions …

1. IP address should be same as of primary Networker?

No – this is most likely not possible in the field. Especially not on a fully routed server

2. How to change browse and Retention policy of newly installed networker on DR site before performing disaster recovery?

Browse policy with NW 9.1? – it disappeared with NW 9.0

Retention policy? – it will be recovered with the resources as part of the DR process.

3. As on DR Data domain hostname is different from that of PR DD. Do i have to change DR DD hostname and set same as of PR DD for proper disaster recovery?

I don’t think so. Just configure the new devices names correctly.

NW will rely on the volume name (the volume id), not the device name.

4. Can i restore NDMP backups to local drive of newly installed server?

No. NDMP backup can only be recovered to NDMP clients.

I think it would be possible for NDMP backups using the DSA method. But even if my technical assumption would

be true such will be suppressed by NW itself. Otherwise you will not be able to recover the metadata properly and

bypass the owner’s rights etc. Such will be prevented.

And do not forget your licenses …

However NW will work for a while to give you time to apply for new ones.

Related:

Re: How can I backup VNX File using NetWorker and an FC tape library

The following is a very basic list of tasks to perform, but it gives you an idea on what needs to be done. Many of these tasks are documented in the admin guide NDMP guide, kb articles, and even in this NetWorker community forums.

Start by designing how these hardware are connected to each other.

  • which host will be controlling the jukebox? NetWorker server, VNX, or another NetWorker storage node?
  • Is the jukebox going to be shared? i.e. some drive dedicated to the VNX, and other drives dedicated to nw server?
  • Are the drives shared? i.e. the VNX and nw server can both access the same physical drive?
  • Do you have necessary licenses to allow you to use this setup?

Verify that the NetWorker server can contact the NDMP daemon that is running on the VNX and listening on port 10000 with:

  • inquire -N (vnx hostname)
  • enter the ndmp user account and password.
  • If it does not error , then it should show you a list of tape drives and jukebox that the VNX is connected to.

In NetWorker Management console, configure the VNX storage node:

  • create a storage node for the VNX, and any other storage node that will be accessing the jukebox and tape drives
  • for each storage node, scan for any scsi devices.
  • once scan is completed, there should be an unconfigured jukebox and drive(s). Use NMC to configure this jukebox
  • complete the task by updating the nw jukebox properties as needed.

Once the jukebox is configured, then again in NMC:

  • configure a nw client for the VNX host
  • verify that you a
  • add this to a nw group, policy, worklow, etc…
  • test backups

Related:

Re: ISILON ‘s backup to TSM using NDMP three-way

Firstly, thank you for your message!

In fact, I do not have any NAS that is directly attached to a library/tape drives.

I found some information from TSM documentation where the 3-way NDMP backup is also named as “filer-to-server”.

Below is figure about it.



With the filer-to-server configuration, the library is attached to the DMA (Tivoli Storage Manager Server). The NAS device does not have access to the library, as shown in Figure. This configuration is also known as 3-way NDMP backup. The backup data from the NAS device is transferred over the network (TCP/IP) to the Tivoli Storage Manager server.”



TSM.png

Related:

Re: NDMP backup of Unity file system is timed out after 24 hours of run

Sorry for delay. Karl, your tip was helpful and I was able to avoid 24-hrs timeout.

Now facing another issue when after approximately 5 days, backup session is still active but nothing is actually being copied to DD. So, trying to understand at what end it brakes: NDMP accelerator, DD, Unity.

Logs on NDMP accelerator:

2018-08-08 07:01:17 avndmp Error <11894>: [snapup-/Jira-Filessystem] Send message failed call for 400.

2018-08-08 07:01:17 avndmp Error <11893>: [snapup-/Jira-Filessystem] ndmp socket write, trying to write 4000 bytes, send returned error 32: code 32: Broken pipe

Session log on Avamar side:

2018-08-08 06:28:25 avtar Warning <6568>:Internal Warning: Very large number of entries on TODO queue (139508)

2018-08-08 06:43:14 avtar Info <41437>: Executing a flush (fsync) to keep write stream alive for file “avamar-1521563896/container.1.cdsf” with file handle 1812451331

2018-08-08 06:43:25 avtar Info <8688>: Status 2018-08-08 06:43:25, 11,456,912 files, 1,829,445 directories, 50,861 GB (11,456,912 files, 1.441 GB, 49.00% new) 3227MB 0% CPU (1 open files)

Related:

Re: NDMP FC Ports on Unity arrays

EMC Unity system is the successor of VNX. One main item is that it only can do 3 way NDMP. Meaning the data need to go over the network to the backup server and from there to the media

As the data goes over the network we need a ‘decent’ backbone network to the backup. For this we are using the ‘on board’ ports of the storage processors. This are 10 GB IP fiber ports.

Issue is that if there is not 10 GB fiber network we need a direct connection with the media server. In turn the media servers need to be equip with two 10 GB IP fiber ports and patched directly to the SP’s of the storage system As per my experience use 10 G on port port for the NDMP



-Unity supports 3-way NDMP backups only, not 2-way direct-attached backups

Note: A three-way backup involves: an NDMP backup client running qualified software; an NDMP data server that reads data from the storage system and produces the data stream for backup; and a server running the tape service (reads the data stream and writes it to tape). In a three-way backup, both file system and control data travel across the network, but this network can be dedicated.

–Supports backups of File data using Data Domain, Avamar, etc.

–NDMP backups updated to backup new UFS64 metadata timestamps, GUID, NFSv4 ACL structures atime; mtime; ctime; cvtime; btime; vctime; bctime

–NMDP backups are new format, cannot restore legacy backups containing deduplicated data to a UFS64 file system

–ufs64 backup will be able to backup ufs32 or ufs64 file systems

–Can restore legacy backups to ufs32 or ufs64, but new ufs64 backup can only be restored to ufs64

–Cannot restore legacy deduped files to UFS64

–New server_param to disable IPv6, if necessary

–Latest file timestamp based on BASE_DATE instead of creation date

–Improved support for Dense files

Max NDMP Concurrent Sessions:

Unity 300-500=8

Related:

Avamar 18.1



Avamar 18.1 and Data Domain System Integration Guide

This guide describes how to install, configure, administer, and use a Data Domain system as a backup target for Avamar.



Avamar 18.1 for Windows Servers User Guide

This guide describes how to install the Avamar client for Microsoft Windows, and how to back up and restore data on a Windows server.



Avamar 18.1 for SQL Server User Guide

This guide describes how to install Avamar in a Microsoft SQL Server environment, and how to back up and restore SQL Server databases.



Avamar 18.1 for IBM DB2 User Guide

This guide describes how to install Avamar in an IBM DB2 environment and how to back up and restore DB2 databases.

Avamar 18.1 for SAP with Oracle User Guide

This guide describes how to install Avamar in an SAP environment with Oracle, and how to back up and restore SAP servers with Oracle databases.



Avamar 18.1 for Oracle User Guide

This guide describes how to install Avamar in an Oracle database environment, and how to back up and restore Oracle databases.

Avamar 18.1 for NDMP Accelerator for Oracle ZFS User Guide

This guide describes how to install and configure the Avamar NDMP Accelerator for Oracle ZFS , and how to back up and restore data on Oracle ZFS.



Avamar 18.1 for NDMP Accelerator for EMC NAS Systems User Guide

This guide describes how to install and configure the Avamar NDMP Accelerator for EMC NAS systems, and how to back up and restore data on supported EMC VNX and EMC storage systems.



Avamar 18.1 for NDMP Accelerator for NetApp Filers User Guide

This guide describes how to install and configure the Avamar NDMP Accelerator for NetApp Filers, and how to back up and restore data on supported NetApp filers.



Avamar 18.1 for Lotus Domino User Guide

This guide describes how to install Avamar in a Lotus Domino environment, and how to back up and restore data.

Avamar 18.1 for SharePoint VSS User Guide

This guide describes how to install Avamar in a SharePoint environment, and how to back up and restore data using Avamar with Microsoft Volume Shadow Copy Service (VSS) technology.



Avamar 18.1 for Sybase ASE User Guide

This guide describes how to install Avamar in a Sybase environment, and how to back up and restore Sybase Adaptive Server Enterprise (ASE) databases.

Related:

Re: Re: NDMP backup of Unity file system is timed out after 24 hours of run

Hi everyone,

I’m having the following issue with backing up EMC Unity 600 file system via NDMP.

Because of a file system being pretty large (~60TB), backup does not end within 24 hours which is fine for the first full backup and I had no issues with VMAX when first backup was running up to 48 hours. Here, with Unity 600, backup is canceled on NAS side after exactly 24 hours of running.

Here is the part of an Avamar log related:

2018-07-11 15_53_37-mRemoteNG - confCons.xml.jpg

On the Unity side I can’t find anything more detailed then this:

2018-07-11 16_04_49-mRemoteNG - confCons.xml.jpg

You can see that NDMP snapshot was created and then destroyed after exactly 24 hours but I have no clue why it happens and that’s where I need your help, guys.

Avamar version used – 7.5.1-101

NDMP version – AvamarNDMP-7.5.101-101.x86_64

NDMP was enabled on Unity via web UI by setting the check-mark “NDMP” for the particular NAS. That’s it. No settings like snapTimeout can be performed for Unity systems, as per NDMP user guide.

Related:

NDMP backup of Unity file system is timed out after 24 hours of run

Hi everyone,

I’m having the following issue with backing up EMC Unity 600 file system via NDMP.

Because of a file system being pretty large (~60TB), backup does not end within 24 hours which is fine for the first full backup and I had no issues with VMAX when first backup was running up to 48 hours. Here, with Unity 600, backup is canceled on NAS side after exactly 24 hours of running.

Here is the part of an Avamar log related:

2018-07-11 15_53_37-mRemoteNG - confCons.xml.jpg

On the Unity side I can’t find anything more detailed then this:

2018-07-11 16_04_49-mRemoteNG - confCons.xml.jpg

You can see that NDMP snapshot was created and then destroyed after exactly 24 hours but I have no clue why it happens and that’s where I need your help, guys.

Avamar version used – 7.5.1-101

NDMP version – AvamarNDMP-7.5.101-101.x86_64

NDMP was enabled on Unity via web UI by setting the check-mark “NDMP” for the particular NAS. That’s it. No settings like snapTimeout can be performed for Unity systems, as per NDMP user guide.

Related: