Tech Tier 2
Wednesday, March 14, 2018
Tuesday, February 2, 2016
NetApp: Disabling snapshot for a volume on Data OnTAP
Sometimes, you need to disable snapshots for a volume, and the command line makes it so much easier.
Why in the world would someone want to disable a perfectly good feature of NetApp NAS Storage? Server/data migration for one. Disabling it temporarily will prevent the volume from filling up the snapshot directory. Maybe your volume doesn't need snapshots such as iscsi luns (data always changing, and can not be recoverable even with snapshots- such as oracle data dirs, in which case snapshots are useless).
You have to perform simple but important tasks. If your volume has a schedule, turn it off.
That takes care of that. Next step is to disable the automatic snapshot option.
Now if you issue
Lastly, you'll probably want to disable the display of the .snapshot directory. Not really a biggie if the qtree/vol is NTFS security style. But in UNIX, you'll see ".snapshot" in
Why in the world would someone want to disable a perfectly good feature of NetApp NAS Storage? Server/data migration for one. Disabling it temporarily will prevent the volume from filling up the snapshot directory. Maybe your volume doesn't need snapshots such as iscsi luns (data always changing, and can not be recoverable even with snapshots- such as oracle data dirs, in which case snapshots are useless).
You have to perform simple but important tasks. If your volume has a schedule, turn it off.
filer> snap sched volname
Volume volname: 2 4 8@2,4,6,12,164
filer> snap sched volname 0 0 0
filer> snap sched volname
Volume volname: 0 0 0
That takes care of that. Next step is to disable the automatic snapshot option.
filer> vol options volname nosnap on
Now if you issue
vol options vol
You should see an option that says nosnap=on
.Lastly, you'll probably want to disable the display of the .snapshot directory. Not really a biggie if the qtree/vol is NTFS security style. But in UNIX, you'll see ".snapshot" in
ls -la
.filer> vol options volname nosnapdir on
Easiest method for creating OSX Mavericks USB Installer
Here is the easiest method to create your OSX Mavericks installer:
sudo
"/Applications/Install OS X
Mavericks.app/Contents/Resources/createinstallmedia" --volume
"/Volumes/Untitled" --applicationpath "/Applications/Install OS X
Mavericks.app" --nointeraction
If that's what you were looking for, then you really don't need to read
any further. If you're a newcomer and need a little more information,
read on:
Before the above command will work for you, you need to plug in your USB
stick and format it using Disk Utility. You'll need a minimum of 8GB,
or it will not work. Partition it and format it using Mac OS Extended
(Journaled). Then run the above command, adjusting the path after
--volume to the path to your mounted USB stick (NOT /Volumes/Macintosh
HD or whatever your system drive is!).
The second thing you need to do is to download the app through the Mac App Store. You can do this even if you have already installed OSX Mavericks; once the installer has downloaded and launched the welcome screen, hit ⌘Q to quit from the actual installer (Or Menu -> Quit). The files will still be at /Applications.
The second thing you need to do is to download the app through the Mac App Store. You can do this even if you have already installed OSX Mavericks; once the installer has downloaded and launched the welcome screen, hit ⌘Q to quit from the actual installer (Or Menu -> Quit). The files will still be at /Applications.
Once you're done (it took me around 20 minutes for the creation process
to complete), plug it into another system and reboot, holding Option to
bring up the disk selection. Select the disk and you should be off to
installing OSX Mavericks from USB.
Tuesday, August 7, 2012
RSOP - Invalid Name Space
Recently had an issue where an entire site was not downloading domain policies. After a thorough search and different attempts to fix the issue I came across a batch file that I want to list here for future reference:
make the following into a batch file
net stop winmgmt
pause
c:
cd c:\windows\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
mofcomp exwmi.mof
mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
mofcomp exmgmt.mof
After running this re-run the GPUPDATE /force
make the following into a batch file
net stop winmgmt
pause
c:
cd c:\windows\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
mofcomp exwmi.mof
mofcomp -n:root\cimv2\applications\exchange wbemcons.mof
mofcomp -n:root\cimv2\applications\exchange smtpcons.mof
mofcomp exmgmt.mof
After running this re-run the GPUPDATE /force
Subscribe to:
Posts (Atom)