Flexvols NetApp FlexClone technology

 
Thread Tools Search this Thread
Special Forums Hardware Flexvols NetApp FlexClone technology
# 1  
Old 01-06-2015
Flexvols NetApp FlexClone technology

Hello,

Please help me understand Copy on Write technology in reference to Flexvols. NetApp FlexClone technology

This is in reference to Snap Clone: Instant, self-serviced database-on-demand

Best regards,
Vishal
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Netapp filer details - command?

What command can I use to find out details about a netapp filer. I have a directory that is a filer i would like to know details about the source host/folder that it points to. Thanks. (2 Replies)
Discussion started by: jjohnson
2 Replies

2. AIX

Netapp iscsi lun

Hi, I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name. Please share me the steps to complete this requirements. Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies

3. UNIX for Advanced & Expert Users

mpxio in Solaris10 with NetApp FAS3140 problem

we have a v440 SUN machine with a NetApp FAS3140 SAN storage, the v440 got 2 HBA qlogic cards both connected to the switch side in NetApp 3140, zoning in netapp configured proberly and luns are adversitesed to the SUN machine, the problem i am facing is that when i try to configure the mpxio i am... (7 Replies)
Discussion started by: q8devilish
7 Replies

4. Filesystems, Disks and Memory

NFSv4 on Netapp and Redhat 5.3 as Client

Hi Folks! I'm new in using NFSv4 and do have a little trouble. I had a partition working with NFSv3, at the beginning i couldn't see on the client the German umlauts letters {ö,ä,ü} a manipulation of the LANG environment variable helped and the filenames with this letters were shown normally... (2 Replies)
Discussion started by: oku
2 Replies

5. Filesystems, Disks and Memory

qtree & quota in netapp

Hi All, What will exactly happen? if I run "quota off" and "quota on" after removing qtree in a netapp Due to this any slowness/quota changes will occur for any other qtrees? Thanks (3 Replies)
Discussion started by: Tlogine
3 Replies

6. Solaris

Can't see Netapp LUN on Solaris using LPFC after reboot.

Hi, I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies

7. Cybersecurity

netapp security

Hi all Background some of the users shuold have access to a folder on the netapp and for other users the access should be denied Question How can I doing that ? Thanks at advance Sam (3 Replies)
Discussion started by: skfn1203
3 Replies

8. Solaris

Use DFM Netapp 3.01 R1 on Solaris 8

I have this problem when i integrate a new san switch in DFM 3.01 R1 : dfm fcswitch add switchname1 Error: Host switchname2 (11197) already exists. switchname2 is a similar san switch but in another fabric, switchname2 is already integrated in DFM database. Bests Regards Olivier (2 Replies)
Discussion started by: omainfroy
2 Replies

9. Filesystems, Disks and Memory

backup NetApp using dump command

I have been trying to backup my NetApp /vol/vol0 data to local tape drive. It is around 68GB. The tape I am using is DLT tape and should be able to handle 70GB data. However, dump always aborted around reaching 57~58GB data. Tape drive is attached on NetApp. 1st try to dump /vol/vol0 to... (2 Replies)
Discussion started by: yellowfish
2 Replies
Login or Register to Ask a Question
auth.adm(1M)															      auth.adm(1M)

NAME
auth.adm - activate, deactivate, or query about HP-UX Integrated Login SYNOPSIS
tech_name [ tech_name ] [ tech_name[:tech_name]... ] [ tech_name:parameter=value[:parameter=value]... ]... [ filename ] DESCRIPTION
The command makes it easy to activate, deactivate or query about HP-UX Integrated Login. During activation, sets up a machine to obtain integrated login behavior using any of the following commands: and saves the Integrated Login configuration, specified by and arguments, in the file This configuration file specifies the authentication technologies used to authenticate users on a system. System administrators can specify the technology for system login; where this login technology is unavailable, a fallback technology for system login can also be specified. System administrators can also specify technologies for additional user authentications that will be done after a user has successfully completed the system login phase. Integrated behavior of and is obtained by replacing the current with one that specifies the behavior requested by the arguments. auth.adm provides an option of enabling the nsswitch for DCE technology. The is updated with "dce" keyword if this option has been selected. In this scenario the name service requests for user/group information will be obtained from DCE depending on the configuration. After NSS switch is enabled, an option is provided to export the DCE user/group information to and via a cron job. program could also be run manually to do this job. Upon deactivation, restores files that were present on the system before Integrated Login was installed. It also removes the configuration file. When making a query, reads the file and prints the result of the query to stdout or to filename specified by the argument. All actions performed by are logged into the file ARGUMENTS
recognizes the following arguments: activates HP-UX Integrated Login. tech_name an abbreviated name representing an authentication technology. Starting with the 10.0 release, the tech_name's supported are: for DCE Registry for /etc/passwd and other HP-UX login technologies. tech_name specifies the technology used for system login. tech_name specifies the technology used for fallback login. tech_name[:tech_name]... specifies technologies used for additional authentications after a user has been successfully logged in to a system. tech_name:parameter=value[:parameter=value]... specifies configurable parameters applicable to a technology. Parameters for different technologies can be specified by repeating the argument. Starting with the 10.30 release, the configurable parameters supported include the following: Timeout (in seconds) on communications with a technology. Default values for TIMEOUT are as follows. 180 seconds ignored Password expiration warning period (in days). If the user's password is due to expire within the specified number of days, the user receives a warning message during login. This parameter applies to DCE technology only. If this parameter is not specified, no warning is given. Password force-change period (in days). If the user's password is due to expire within the specified number of days, the user is forced to change the password before login is allowed. This parameter applies to the DCE technology only. If this parameter is not specified, a password change is not forced. Enable DCE TGT to be forwardable. When forwarding a user's DCE TGT from machine A to machine B, it enables the user from machine A to reuse its Kerberos credentials on machine B. A parameter value is required, but its content is ignored. This parameter applies to DCE technology only. deactivates HP-UX Integrated Login. makes a query about the current Integrated Login configuration. filename prints result of a query to filename. EXAMPLES
The following command activates HP-UX Integrated Login. The configuration is set to login the user upon successful password verification by DCE. In the case where DCE is not available, a fallback for login via /etc/passwd or another HP-UX technology is configured. (Note that this strategy is effective only if the HP-UX password and DCE password are identical.) The following command activates HP-UX Integrated Login. The configuration is set to login the user upon successful password verification by /etc/passwd or another HP-UX technology. After machine access has been granted to the user, the configuration specifies that a DCE login should also be done. RETURN VALUE
returns one of the following: Successfully completed Error(s) occurred WARNING
If activation or deactivation fails to complete, the error(s) should be corrected and re-execution of the activation/deactivation should be done. cannot deactivate a failed activation. NOTE
auth.adm will restart the pwgrd daemon after the ilogin daemon is started, if it was already running. AUTHOR
was developed by HP. FILES
log file containing records of actions performed by SEE ALSO
auth.adm(1M)