.\" $Id: pathownerignore.5,v 1.1.64.2 2006/04/26 18:52:18 castrv Exp $ Copyright (c) 2000-2005 EMC Corporation. .\" Copyright (c) 2000-2005 EMC Corporation. .\" All rights reserved. .TH pathownerignore 5 "Aug 23, 06" "StorEdge EBS 7.3.2" .SH NAME pathownerignore \- ignore path-ownership rules during scheduled saves .SH SYNOPSIS /pathownerignore .SH DESCRIPTION In a clustered environment, the Sun StorEdge EBS software must distinguish between filesystems associated with the physical client, and those that are managed by a resource group (a virtual client). These criteria are referred to as the path-ownership rules. These rules determine which client index a save set is written to. .PP If a filesystem owned by a virtual client is defined in the save set list for a physical client resource, by default the filesystem .B will not be backed up during a scheduled save. The same is true for a filesystem owned by a physical client defined in the save set list for a virtual client resource. In both cases, the filesystem is omitted. This occurs because the Sun StorEdge EBS software views the client (which owns the filesystem) as not having matched the client of the current scheduled save. .PP To check the Sun StorEdge EBS path-ownership rule: .PP 1. Run the following command on the Sun StorEdge EBS server: .RS # savegrp -p -c .B client_name .RE .PP 2. Review which filesystems are owned by client_name. This procedure is part of the normal cluster installation setup. For detailed instructions, refer to the appropriate EMC Sun StorEdge EBS Installation Guide. .PP To test for the existence of misappropriated save sets, run a test probe with the verbose option set. The command output will warn you to which client indexes a save set will be saved. For example: .RS # savegrp -pv -c .B client_name group_name .RE .PP To ignore Sun StorEdge EBS default path-ownership rules, you can create the /pathownerignore file. This file causes the Sun StorEdge EBS software to back up the filesystem in question; however, the filesystem will be saved under the index of its correct owner. Creating the /pathownerignore file is not recommended, but it might be required under special circumstances. The /pathownerignore file does not override the default path-ownership rules. It causes the path-ownership rules to be ignored when determining if a filesystem should be backed up during a scheduled save. .SH SEE ALSO .BR save (8), .BR savegrp (8), .BR savefs (8) .SH NOTES To override the path-ownership rules and have a save set written to an index other than its default owner, one must use the "save -c .B client_name " command. Refer to .B save (8) for more information.