svc:> select dns/client
svc:/network/dns/client> setprop config/search = astring: \
(“us.company.com” “eu.company.com” “companya.com” “companyb.com” “company.com” )
svc:/network/dns/client> setprop config/nameserver = net_address: \
( 220.127.116.11 18.104.22.168 )
svc:/network/dns/client> select dns/client:default
svc:/network/dns/client:default> select name-service/switch
svc:/system/name-service/switch> setprop config/host = astring: “files dns”
svc:/system/name-service/switch> select system/name-service/switch:default
# svcadm enable dns/client
# svcadm refresh name-service/switch
# grep host /etc/nsswitch.conf
hosts: files dns
# cat /etc/resolv.conf
# opyright (c) 2011, Oracle and/or its affiliates. All rights reserved.
# WARNING: THIS FILE GENERATED FROM SMF DATA.
# DO NOT EDIT THIS FILE. EDITS WILL BE LOST.
# See resolv.conf(4) for details.
search us.company.com eu.company.com companya.com companyb.com company.com
I’ve tried using a share for time machine before, but due to the nature of how time machine works it eventually consumed all the spare space that is available on that particular share.
bring on zfs quotas… (my drive on my mini mac is 100GB, so 200GB should be enough for a few variations)
zfs set quota=200G unprotected/timemachine
This adds a artificial limit to your zfs filesystem, making sure that time machine does not consume more than 200 gigabytes of space.
NFS is your best bet, i’ve created a NFS share like so…
zfs create unprotected/timemachine
zfs set sharenfs=on unprotected/timemachine
Posted in Apple, Networking, Solaris Express, Storage |
Tagged backups, cifs, mac, mini mac, quota, share, timemachine, zfs |
You’ll need these two packages installed;
First ensure that the DHCP service is running. Go into the “services” gui and tick the box to enable the DHCP server.
now from commandline run…
From edit menu choose “network wizard”, step through the wizard (defautls are o.k i you have a fixed IP already assigned to your opensolaris box)
From edit menu choose “address wizard”
If you step through the wizard (the following is an example of what i have choosen)
Choose Text files
Leave default path of /var/dhcp
Do not manage hosts records
Default lease of 1 day (clients can renew their leases)
DNS Domain “yourdomainname”, also add your DNS here
Network Address & subnet (should be pre populated if you have fixed IP on your host)
Network Type (LAN), Routing (leave as default)
I have left NIS blank
I have left NIS+ blank
Setup iSCSI target using comstar —
pkg install -v storage-server
pkg install pkg:/SUNWiscsit
svcadm enable stmf
svcadm enable svc:/network/iscsi/target:default
reboot — -r
Create the iSCSI store —
zfs create -V 100G DataPool/TestDatastore1
sbdadm create-lu /dev/zvol/rdsk/DataPool/TestDatastore1
stmfadm create-hg ESX4-group
stmfadm add-hg-member -g ESX4-group wwn.2100001b329711bd wwn.2101001b32b711bd
stmfadm add-view -h ESX4-group -n 0 600144F03EBEC50000004BA86E460001
stmfadm list-lu -v
Move the downloaded tar.gz file into /var/spool/pkg/
mv CrashPlan_2010-03-08_Solaris.tar.gz /var/spool/pkg/
Unpack the archive.
tar -xzvf CrashPlan_2010-03-08_Solaris.tar.gz
Install the CrashPlan package:
Start CrashPlan Engine:
sudo /opt/sfw/crashplan/bin/CrashPlanEngine start
Start CrashPlan Desktop:
To enable CrashPlan PRO as a service (as root):
svccfg import /opt/sfw/crashplan/bin/crashplan.xml
svcadm enable crashplan
check that the service has come online proplery (then load client)
svcs -a | grep crashplan
online 21:18:43 svc:/crashplan:default
simple but functional script to check if your zpools are healthy and send email if they are not…
Unfortunately if you have accidentally added a single drive into your raidz pool at the top-level there is no way to just remove the non redundant disk. Your pool is now
dependant on this disk.
If you want your pool to be just raidz vdevs, then you will need to backup your data, destroy your pool, create a new pool, and restore your data.
There is no current way to remove a top-level vdev from a pool.
dmesg | tail
Shows the last few entries in the system log.
OpenSolaris is Dead.
What follows is an email sent internally to Oracle Solaris Engineers which describes Oracle’s true intentions toward the OpenSolaris project and the future of Oracle Solaris.
This concludes over four years that I (and many other external contributors) have worked on the OpenSolaris project. This is a terrible sendoff for countless hours of work – for quality software which will now ship as an Oracle product that we (the original authors) can no longer obtain on an unrestricted basis.
I can only maintain that the software we worked on was for the betterment of all, not for any one company’s bottom line. This is truly a perversion of the open source spirit.
OpenSolaris users have two choices. They can wait for Oracle to deliver a free Solaris binary called Solaris 11 Express, available with optional support, by the end of the year, ahead of the full release of the next-generation commercial Solaris 11 rev next year or they can hope that Illumos, the new Nextenta-led OpenSolaris fork, turns into something.
I found this on opensolaris forums…. A nice way to increase your swap without the need for a reboot.
First check your current swap size and details;
Then create a temp swap zfs store and delete and increase swap
zfs create -V <old size> rpool/swp
swap -a /dev/zvol/dsk/rpool/swp
swap -d /dev/zvol/dsk/rpool/swap
zfs destroy rpool/swap
zfs create -V <new size> rpool/swap
swap -a /dev/zvol/dsk/rpool/swap
swap -d /dev/zvol/dsk/rpool/swp
zfs destroy rpool/swp
If you are happy to reboot…
zfs set volsize=8G rpool/swap