Home | History | Annotate | Download | only in man1m
 te
 CDDL HEADER START

 The contents of this file are subject to the terms of the
 Common Development and Distribution License (the "License"). 
 You may not use this file except in compliance with the License.

 You can obtain a copy of the license at CDDL.txt
 or http://www.opensolaris.org/os/licensing.
 See the License for the specific language governing permissions
 and limitations under the License.

 When distributing Covered Code, include this CDDL HEADER in each
 file and include the License file at CDDL.txt.
 If applicable, add the following below this CDDL HEADER, with the
 fields enclosed by brackets "[]" replaced with your own identifying
 information: Portions Copyright [yyyy] [name of copyright owner]

 CDDL HEADER END
 Copyright 2006 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.
 scsnapshot 1M "22 Jun 2006" "Sun Cluster 3.2" "System Administration Commands"
 NAME
scsnapshot - retrieve configuration data about resource groups, resource types, and resources, and generate a shell script

 SYNOPSIS


scsnapshot [-s scriptfile] [-o imagefile]






scsnapshot [-s scriptfile] oldimage newimage




 DESCRIPTION

Note - 


Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more information about the object-oriented command set, see the Intro(1CL) man page.




The scsnapshot tool retrieves information from the Cluster Configuration Repository (CCR) about configuration data that is related to resource groups, resource types, and resources. The scsnapshot tool formats the configuration data as a shell script
that can be used for the following purposes:




To replicate configuration data on a cluster that has no configured resource groups, resource types, and resources






To upgrade configuration data on a cluster that has configured resource groups, resource types, and resources




The scsnapshot tool retrieves configuration data only from the CCR. Other configuration data is ignored. The scsnapshot tool does not take into account the dynamic state of different resource groups, resource types, and resources.


You can use this command only in the global zone.

 OPTIONS

The following options are supported by the scsnapshot tool. If you use an incorrect command option, the correct way to use the command option is displayed.


.na
-s scriptfile
.ad


Stores the generated script in a file called scriptfile.
You can use this option only in the global zone.
If this option is not specified, the generated script is written to the standard output.
If a file called scriptfile already exists, it is renamed as scriptfile.old, and a new file called scriptfile is created. If a file called scriptfile.old already
exists, it is overwritten.





.na
-o imagefile
.ad


Stores the generated image file in a file called imagefile.
You can use this option only in the global zone.
If this option is not specified, an image file is not generated.
If a file called imagefile already exists, it is renamed as imagefile.old, and a new file called imagefile is created. If a file called imagefile.old already
exists, it is overwritten.





.na
oldimage
.ad


Specifies an image file that contains the old configuration data.





.na
newimage
.ad


Specifies an image file that contains the new configuration data.




 EXTENDED DESCRIPTION

The output of the scsnapshot tool is an executable Bourne shell-based script. Before you run the script, you might need to manually change some properties to reflect the features of your host.


The script compares the following characteristics of the local cluster to the cluster where the script was generated:




Machine architecture






Version of the Solaris Operating System






Version of the Sun Cluster software




If the characteristics are not the same, the script writes an error and ends. A message asks whether you want to rerun the script by using the -f option. The -f option forces the script to run, despite any difference in characteristics.


The script generated by the scsnapshot tool verifies that the Sun Cluster resource type exists on the local cluster. If the resource type does not exist on the local cluster, the script writes an error and ends. A message asks whether you want to install the missing resource
type before you run the script again.


To run a script that is generated by the scsnapshot tool, you need solaris.cluster.resource.modify RBAC authorization. For more information, see the rbac(5) man page.

 USAGE

This section describes how you can use the scsnapshot tool.

 "Retrieving Configuration Data for Resource Groups, Resource Types, and Resources"


scsnapshot [-s scriptfile] [-o imagefile]





Used without the -o option, the scsnapshot tool generates a script that creates configuration data for clusters that do not already have configured resource groups, resource types, and resources. See .


Used with the -o option, the scsnapshot tool produces an image file that represents the configuration data. The image file can be used in further invocations of the scsnapshot tool to upgrade configuration data on a cluster. See .


To use the scsnapshot tool to retrieve configuration data, you need solaris.cluster.resource.read role-based access control (RBAC) authorization. For more information, see the rbac(5) man page.


To track differences between versions of configuration data, store the image files in a source control system such as SCCS.

 "Upgrading Configuration Data for Resource Groups, Resource Types, and Resources"


scsnapshot [-s scriptfile] oldimage newimage





The scsnapshot tool generates a shell script that can be used to upgrade the configuration data that is contained in the oldimage file with the configuration data that is contained in the newimage file.


To use the scsnapshot tool to upgrade configuration data, you do not need specific RBAC authorization.

 EXAMPLES

Example 1 To Generate a Shell Script That Retrieves Configuration Data for Resources Groups, Resource Types, and Resources


The script that is generated in this example is called scriptfile.sh.


example% scsnapshot -s scriptfile.sh





Example 2 To Generate a Shell Script That Retrieves Configuration Data and Stores an Image File


The script that is generated in this example is called scriptfile.sh. The configuration data is stored in an image file called imagefile.


example% scsnapshot -s scriptfile.sh -o imagefile





Example 3 To Generate a Shell Script That Upgrades Configuration Data on One Cluster With Configuration Data From Another Cluster


This example creates a script that upgrades the configuration data on cluster1 to match the configuration data on cluster2. The configuration data for cluster1 is in a file called imagefile1, and the configuration
data for cluster2 is in a file called imagefile2. The name of a shell script is not specified, so the generated script is written to the standard output.


example% scsnapshot imagefile1 imagefile2




 EXIT STATUS

The following exit status codes are returned:


.na
0 
.ad


The command completed successfully.





.na
nonzero
.ad


An error occurred.




 ATTRIBUTES

See attributes(5) for descriptions of the following attributes:







ATTRIBUTE TYPEATTRIBUTE VALUE
AvailabilitySUNWsczu
Interface StabilityEvolving



 SEE ALSO

Intro(1CL), attributes(5), clconfiguration(5CL), rbac(5), rg_properties(5), rt_properties(5), r_properties(5)