Sponsored Content
Operating Systems Solaris Permissions to run ZFS Snapshots Post 302850647 by AndyG on Thursday 5th of September 2013 09:20:43 AM
Old 09-05-2013
Permissions to run ZFS Snapshots

Hi,

I work as an Oracle Technical consultant (mainly DBA related), and I have used ZFS snapshots on previous projects which has helped me a great deal. I often take snapshots before doing some dev work, and then I can roll it back if I want to start again, or if it goes pear shaped!!

I have used the root user in the past, because it was on development servers owned by us or our project. On my current project the servers are controlled by another company, and understandably they don't want to give out the root password and probably not a sudo root.

Are there any ways to give my unix (solaris) user permissions to just be able to create/delete/rollback ZFS snapshots? Otherwise I will need to be reliant on the third party to run them for me, which is probably going to delay me.

Regards,
Andy
 

3 More Discussions You Might Find Interesting

1. Solaris

Recommended Patch Cluster Using ZFS Snapshots

I have a question regarding installing recommended patch clusters via ZFS snapshots. Someone wrote a pretty good blog about it here: Initial Program Load: Live Upgrade to install the recommended patch cluster on a ZFS snapshot The person's article is similar to what I've done in the past. ... (0 Replies)
Discussion started by: christr
0 Replies

2. Solaris

Help with ZFS send permissions

I'm trying to send an incremental ZFS file system from one system to another (Solaris 11.2). When I run this: zfs send -RI 20150429 gpool/zones/zone-name@20150501 | \ ssh dest-host "/usr/sbin/zfs recv -o canmount=off -dFuv bpool" I get Unable to estimate the size of... (1 Reply)
Discussion started by: kmcgrego
1 Replies

3. Solaris

Understanding ZFS Snapshots - why will it utilize space ?

Hi all, I am moving to Solaris11 and is trying to understand how ZFS snapshot works. Chances upon this Oracle Blog and can't wrap my head around it. https://blogs.oracle.com/solaris/understanding-the-space-used-by-zfs-v2 Hope gurus here can shed some light . ======= ... (4 Replies)
Discussion started by: javanoob
4 Replies
VFS_SHADOW_COPY2(8)					    System Administration tools 				       VFS_SHADOW_COPY2(8)

NAME
vfs_shadow_copy2 - Expose snapshots to Windows clients as shadow copies. SYNOPSIS
vfs objects = shadow_copy2 DESCRIPTION
This VFS module is part of the samba(7) suite. The vfs_shadow_copy2 VFS module functionality that is similar to Microsoft Shadow Copy services. When setup properly, this module allows Microsoft Shadow Copy clients to browse "shadow copies" on Samba shares. This is a 2nd implementation of a shadow copy module. This version has the following features: 1. You don't need to populate your shares with symlinks to the snapshots. This can be very important when you have thousands of shares, or use [homes]. 2. The inode number of the files is altered so it is different from the original. This allows the 'restore' button to work without a sharing violation. This module is stackable. CONFIGURATION
vfs_shadow_copy2 relies on a filesystem snapshot implementation. Many common filesystems have native support for this. Filesystem snapshots must be mounted on specially named directories in order to be recognized by vfs_shadow_copy2. The snapshot mount points must be immediate children of a the directory being shared. The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss, where: o YYYY is the 4 digit year o MM is the 2 digit month o DD is the 2 digit day o hh is the 2 digit hour o mm is the 2 digit minute o ss is the 2 digit second. The vfs_shadow_copy2 snapshot naming convention can be produced with the following date(1) command: TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S OPTIONS
shadow:snapdir = SNAPDIR Path to the directory where snapshots are kept. shadow:basedir = BASEDIR Path to the base directory that snapshots are from. shadow:fixinodes = yes/no If you enable shadow:fixinodes then this module will modify the apparent inode number of files in the snapshot directories using a hash of the files path. This is needed for snapshot systems where the snapshots have the same device:inode number as the original files (such as happens with GPFS snapshots). If you don't set this option then the 'restore' button in the shadow copy UI will fail with a sharing violation. EXAMPLES
Add shadow copy support to user home directories: [homes] vfs objects = shadow_copy2 shadow:snapdir = /data/snaphots shadow:basedir = /data/home CAVEATS
This is not a backup, archival, or version control solution. With Samba or Windows servers, vfs_shadow_copy2 is designed to be an end-user tool only. It does not replace or enhance your backup and archival solutions and should in no way be considered as such. Additionally, if you need version control, implement a version control system. VERSION
This man page is correct for version 3.2.7 of the Samba suite. AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. Samba 3.5 06/18/2010 VFS_SHADOW_COPY2(8)
All times are GMT -4. The time now is 06:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy