Problem creating Ignite UX file

[welshowen]

I’m trying to create an Ignite backup on one of my servers, and get the following error:

nfs mount: fhs-qw5:/var/opt/ignite/recovery/archives/fhs-qw5: Permission denied
ERROR: Unable to mount or write
fhs-qw5:/var/opt/ignite/recovery/archives/fhs-qw5
On fhs-qw5 you may need to:
mkdir -p /var/opt/ignite/recovery/archives/fhs-qw5
chown bin:bin /var/opt/ignite/recovery/archives/fhs-qw5

If the OS on fhs-qw5 is 11.31 or later, vi /etc/dfs/dfstab. The
/etc/dfs/dfstab file on "fhs-qw5" should contain the entry: "share -F
nfs -o sec=sys,anon=2,rw=
/var/opt/ignite/recovery/archives/fhs-qw5". Where is replaced
by a fully qualified client name.
After editing the /etc/dfs/dfstab file, run "shareall -F nfs"
If you need to change the owner of the directory,
you will also need to re-share the directory.

Otherwise, vi /etc/exports. The /etc/exports file on "fhs-qw5" should
contain the entry: "/var/opt/ignite/recovery/archives/fhs-qw5
-anon=2,access=fhs-qw5".
After editing the /etc/exports file, run exportfs -av
If you need to change the owner of the directory,
you will also need to re-export the directory.

See make_net_recovery(1M) for more information.
ERROR: Failed to Create NFS mount Archive directory.

Needless to say, I have followed all the instructions that the error message suggests, and non of it makes any difference.

I didn’t have a /etc/exports file, but I have created one with the required input.

Also, I tried changing the entry oin /etc/dfs/dfstab so that anon=root instead of anon=2. This also had no effect.

I can’t see any simple permissions problems, the /archives folder is owned by bin:bin.

Any idea’s on where to go from here?

Strangely, I have five other servers using the same configuration, and they create these backups with no problem.

Thanks.

[welshowen]

Some more directory info:

/#ll -d /var/opt/ignite/recovery
drwxrwxrwx 5 bin bin 1024 May 1 14:08 /var/opt/ignite/recove
ry
/#ll -d /var/opt/ignite/recovery/archives
drwxrwxrwx 8 bin bin 1024 May 1 13:34 /var/opt/ignite/recove
ry/archives
/#ll -d /var/opt/ignite/recovery/archives/fhs-qw5
drwxrwxrwx 2 bin bin 96 Feb 18 16:42 /var/opt/ignite/recove
ry/archives/fhs-qw5

[Jeff Gyurko]

Have you exported the filesystem you defined in /etc/exports?

Do you have NFS services running (see /etc/rc.config.d/nfsconf). The server you are trying to Ignite should have the NFS_CLIENT bit set to 1. I might try to stop & start the NFS services. Client stop, core stop, core start, client start.

Can you mount the directory outside of Ignite?
mkdir /junk
mount :/exportedFS /junk

Try the export without the anon parameter. That only says who the FS will be mounted as if it's done anonymously.

[Rcky Mntere]

I had the exact same issue...

System HP-UX xxxx B.11.31 U ia64

Note: hostname=client

I opted to create a separate lvol for the ignite recovery:
Filesystem kbytes used avail %used Mounted on
/dev/vg01/lvol11 50331648 706513 46523570 1% /ignite

root@pluto> /ignite #
ll -R *

ll
total 0
drwxr-xr-x 2 root sys 96 May 20 14:29 depots
drwxr-xr-x 2 root root 96 Dec 3 11:46 lost+found
drwxr-xr-x 3 bin bin 96 May 20 14:30 recovery

recovery:
total 0
drwxr-xr-x 3 bin bin 96 May 20 16:05 archives

recovery/archives:
total 0
drwxr-xr-x 2 bin bin 96 May 20 16:06 hostname

recovery/archives/hostname:
total 1415632
-rw------- 1 bin sys 723484672 May 20 16:13 2009-05-20,16:06

my /etc/dfs/dfstab file:
share -F nfs -o anon=2 /var/opt/ignite/clients
share -F nfs -o sec=sys,anon=2, \ rw=polaris.dpsk12.org /ignite/recovery/archives/hostname


It did not work until after I executed:
shareall -F nfs

Good luck

[Shailendran V Naidu]

Hi,
Please run the following from the Client and make sure the client has the visibility of the /var/opt/ignite directory:

#showmount -e

[welshowen]

fhs-qw5:[/] # showmount -e fhs-dev
export list for fhs-dev:
/var/opt/ignite/clients (everyone)
/var/opt/ignite/recovery/archives/fhs-dev fhs-dev,fhs-qw1,fhs-qw2,fhs-qw3,fhs-qw
4,fhs-qw5
/var/opt/ignite/recovery/archives/fhs-qw1 fhs-dev,fhs-qw1,fhs-qw2,fhs-qw3,fhs-qw
4,fhs-qw5
/var/opt/ignite/recovery/archives/fhs-qw2 fhs-dev,fhs-qw1,fhs-qw2,fhs-qw3,fhs-qw
4,fhs-qw5
/var/opt/ignite/recovery/archives/fhs-qw3 fhs-dev,fhs-qw1,fhs-qw2,fhs-qw3,fhs-qw
4,fhs-qw5
/var/opt/ignite/recovery/archives/fhs-qw4 fhs-dev,fhs-qw1,fhs-qw2,fhs-qw3,fhs-qw
4,fhs-qw5
/var/opt/ignite/recovery/archives/fhs-qw5 fhs-dev,fhs-qw1,fhs-qw2,fhs-qw3,fhs-qw
4,fhs-qw5

[Steven E. Protter]

Shalom,

To write an Ignite backup the server writing the files needs write permissions.

This error appears to be a problem of insufficient rights on the NFS side, not local server side.

So ownership and permission may look good but if the NFS mount is read only this is not going to work until you get full write perms.

SEP

[welshowen]

Oops, sorry all, turned out to be a simple problem.

The /etc/hosts entry on the NFS server was wrong. The server being backed up was pointing to the correct destination, but the hosts entry couldn't verify the incoming connection.

Thanks all for your contributions.

[welshowen]

As above