Permissions to run ZFS Snapshots


 
Thread Tools Search this Thread
Operating Systems Solaris Permissions to run ZFS Snapshots
Prev   Next
# 1  
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
 
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. 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

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

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
Login or Register to Ask a Question
SNAPPER-CONFIGS(5)					  Filesystem Snapshot Management					SNAPPER-CONFIGS(5)

NAME
snapper-configs - Configuration files for snapper configs DESCRIPTION
Each file /etc/snapper/configs/* describes a snapper config. VARIABLES
The following is a list of variables that can be present in the configuration file. Boolean values must be "yes" or "no". SUBVOLUME=path Path of the subvolume or mount point. There is no default value. The value must always be specified. FSTYPE=value Filesystem type for the subvolume. Default value is "btrfs" but it's recommended to always specify the filesystem type. ALLOW_USERS=users List of users allowed to operate with the config. The user-names must be separated by spaces. Spaces in usernames can be escaped with a "". Default value is "" but "root" is always implicitly included. ALLOW_GROUPS=groups List of groups allowed to operate with the config. The group-names must be separated by spaces. Spaces in group-names can be escaped with a "". Default value is "". BACKGROUND_COMPARISON=boolean Defines whether pre and post snapshots should be compared in the background after creation. Default value is "no". NUMBER_CLEANUP=boolean Defines whether the number cleanup algorithm should be run for the config. Default value is "no". NUMBER_MIN_AGE=seconds Minimal age for snapshots to be deleted by the number cleanup algorithm. Default value is "1800". NUMBER_LIMIT=number Defines how many snapshots the number cleanup algorithm should keep. The youngest snapshots will be kept. Default value is "50". TIMELINE_CREATE=boolean Defines whether hourly snapshots should be created. Together with the timeline cleanup algorithm this will create a collection of snapshots with more snapshots is the near past and less snapshots in the far past. Default value is "no". TIMELINE_CLEANUP=boolean Defines whether the timeline cleanup algorithm should be run for the config. Default value is "no". TIMELINE_MIN_AGE=seconds Minimal age for snapshots to be deleted by the timeline cleanup algorithm. Default value is "1800". TIMELINE_LIMIT_HOURLY=number Defines how many hourly snapshots the timeline cleanup algorithm should keep. An hourly snapshots is the first snapshot in an hour. The youngest hourly snapshots will be kept. Default value is "10". TIMELINE_LIMIT_DAILY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". TIMELINE_LIMIT_MONTHLY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". TIMELINE_LIMIT_YEARLY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". EMPTY_PRE_POST_CLEANUP=boolean Defines whether the empty-pre-post cleanup algorithm should be run for the config. Default value is "no". EMPTY_PRE_POST_MIN_AGE=seconds Minimal age for snapshots to be deleted by the empty-pre-post cleanup algorithm. Default value is "1800". HOMEPAGE
http://snapper.io/ AUTHORS
Arvin Schnell <aschnell@suse.de> SEE ALSO
snapper(8), snapperd(8) 0.1.7 2013-07-09 SNAPPER-CONFIGS(5)