Admitting Need – The Reality Choice
I realize I’m not God. I admit that I am powerless to control my tendency to do the wrong thing and that my life is unmanageable.
1. We admitted we were powerless over alcohol — that our lives had become unmanageable.
“Happy are those who know they are spiritually poor.” Matthew 5:3 (TEV)
Getting Help – The Hope Choice
I earnestly believe that God exists, that I matter to him, and that he has the power to help me recover.
2. Came to believe that a Power greater than ourselves could restore us to sanity.
“For God is working in you, giving you the desire and the power to do what pleases him.” Phillippians 2:13 (NLT)
Letting Go – The Commitment Choice
I consciously choose to commit all my life and will to Christ’s care and control.
3. Made a decision to turn our will and our lives over to the care of God as we understood him.
“Come to me, all of you who are weary and over-burdened, and I will give you rest!” Matthew 11:28 (PH)
Coming Clean – The Housecleaning Choice
I openly examine and confess my faults to myself, to God, and to someone I trust.
4. Made a searching and fearless moral inventory of ourselves.
5. Admitted to God, to ourselves, and to another human being the exact nature of our wrongs.
“No matter how deep the stain of your sins, I can take it out and make you as clean as freshly fallen snow.” Isaiah 1:18 (LB)
Making Changes – The Transformation Choice
I voluntarily submit to every change God wants to make in my life and humbly ask Him to remove my character defects.
6. Were entirely ready to have God remove all these defects of character.
7. Humbly asked him to remove our shortcommings.
“…let God transform you inwardly by a complete change of your mind.” Romans 12:2 (GNT)
Repairing Relationships – The Relationship Choice
I evaluate all my relationships, offer forgiveness to those who have hurt me, and make amends for harm I’ve done to others, except when to do so would harm them or others.
8. Made a list of all persons we had harmed, and became willing to make amends to them all.
9. Make direct amends to such people wherever possible, except when to do so would injure them or others.
Step 10 of AA doesn’t really correspond/or match one of Life’s Healing Choices.
10. Continued to take personal inventory and when we were wrong promptly admitted it.
“Happy are those who are merciful to others…Happy are those who work for peace.” Matthew 5:7,9
Maintaining Momentum – The Growth Choice
I reserve a daily quiet time with God for self-examination, bible reading, and prayer in order to know God and his will for my life and to gain the power to follow his will.
11. Sought through prayer and meditation to improve our conscience contact with God, as we understood him, praying only for the knowledge of His will for us and the power to carry that out.
“Test yourselves to make sure you are solid in the faith. Don’t drift along taking everything for granted. Give yourselves regular checkups.” 2 Corinthians 13:5 (MSG)
Recycling Pain – The Sharing Choice
I yield myself to God to be used to bring this good news to others, both by my example and by my words.
12. Having had a spiritual awakening as a result of these Steps, we tried to carry this message to alcoholics, and to practice these principals in all our affairs.
[God] comforts us in all our troubles so that we can comfort others. When they are troubled, we will be able to give them the same comfort God has given us. 2 Corinthians 1:4 (NLT)
Notes from sermon by Pastor Leigh Harrison - 1/31/2010
Luke 11:9 “And so I tell you, keep on asking, and you will be given what you ask for. Keep on looking and you will find. Keep on knocking, and the door will be opened.” NLT
First: We ask…How do we ask? With FAITH!
1. God Is and He Cares
Heb 11:6 “Anyone who wants to come to him must believe that there is a God and that he rewards those who sincerely seek him.” NLT
Mt 6:31-32 “So do not worry, saying, `What shall we eat…or drink…or wear?`..you heavenly Father knows that you need them.” NIV
Examples of netbackup restores:
To restore files listed in a file named restore_list by using the most
recent backups, enter the following:
bprestore -f restore_list
At console> halt
CFE> bye
CTRL-C to go to special boot menu
Choose option 4a to initialize disks and create a flex root volume.
system> setup
The setup command will rewrite the /etc/rc, /etc/exports,
/etc/hosts, /etc/hosts.equiv, /etc/dgateways, /etc/nsswitch.conf,
and /etc/resolv.conf files, saving the original contents of
these files in .bak files (e.g. /etc/exports.bak).
Are you sure you want to continue?
system> reboot
software install url
system> software install http://nbctx01/NetApp/FAS270/732_setup_m.exe
system> software install http://www.myserver.com/example/R72/pc/72_setup_i.exe
software: installing software, this could take a few minutes …software: installation completed.Please type “download” to load the new software and “reboot” subsequently for changes to take effect.system>
download
Operator requested download completed. Then…
reboot
| LTO Tape Capacities | |||
| Type | Released | Native | Compressed |
| LTO-1 | 2000 | 100GB | 200GB |
| LTO-2 | 2003 | 200GB | 400GB |
| LTO-3 | 2005 | 400GB | 800GB |
| LTO-4 | 2007 | 800GB | 1.6TB |
| LTO-5 | TBA | 1.6TB | 3.1TB |
| LTO-6 | TBA | 3.2TB | 6.4TB |
| http://www.tapeandmedia.com/dlt_capacity_info.asp | |||
| DLT Drive and Media Specifications and Cleaning Tape Cartridge | |||
| Drive | Media Type | Capacity, MB | Cleaning Tape |
| DLT 2000 | DLTtape III | 10 / 20 | Cleaning Tape III |
| DLT 2000XT | DLTtape IIIXT | 15 / 30 | Cleaning Tape III |
| DLT 4000 | DLTtape IV | 20 / 40 | Cleaning Tape III |
| DLT 7000 | DLTtape IV | 35 / 70 | Cleaning Tape III |
| DLT 8000 | DLTtape IV | 40 / 80 | Cleaning Tape III |
| DLT1 | DLTtape IV | 40 / 80 | DLT I Cleaning |
| DLT VS80 | DLTtape IV | 40 / 80 | DLT I Cleaning |
| DLT VS160 | DLTtape VS1 | 80 / 160 | DLT VS160 Cleaning |
| DLT-V4 | DLTtape VS1 | 160 / 320 | DLT VS160 Cleaning |
| SDLT 220 | Super DLTtape I | 110 / 220 | SDLT Cleaning Tape |
| SDLT 320 | Super DLTtape I | 160 / 320 | SDLT Cleaning Tape |
| SDLT 600 | Super DLTtape II | 300 / 300 | SDLT Cleaning Tape |
| DLT S4 | DLT S4 Tape | 800/1600 | SDLT Cleaning Tape |
| Click on Media Type or Cleaning Tape to see selection for your drive. | |||
| Media | Drives | Capacity | Performance |
| Native - Compressed | Native-Compressed | ||
| SuperDLTtape 1 | SDLT-220 | 110 GB - 220 GB | 11 MB/s - 32 MB/s |
| DLTtape IV - TK88 | DLT1 (Benchmark) | 40 GB - 80 GB | 3 MB/s - 6 MB/s |
| DLT-8000 | 40 GB - 80 GB | 6 MB/s - 12 MB/s | |
| DLT-7000 - Tz89 | 35 GB - 70 GB | 5 MB/s - 10 MB/s | |
| DLT-4000 - Tz88 | 20 GB - 40 GB | 1.50 MB/s - 3.0 MB/s | |
| DLTtape IIIXT - | DLT-2000 XT - | 15 GB - 30 GB | 1.25 MB/s - 2.5 MB/s |
| DLTtape III - TK85 | DLT-2000 - Tz87 | 10 GB - 20 GB | 1.25 MB/s - 2.5 MB/s |
| DLT-600 - Tz86 | 6 GB - | 0.8 MB/s - | |
| DLT-260 - Tz85 | 2.6 GB - | 0.8 MB/s | |
| TAPE MEDIA | MEDIA DESCRIPTION | ||
| Super DLTtape 1 | 1833′ ATOMM with Optical Servo Patterns | ||
| DLTtape IV | 1828′ Advanced super Thin-layer high-Output Metal Media (ATOMM) | ||
| DLTtape III XT | 1828′ Metal Particle Media (MP) | ||
| DLTtape III | 1200′ Metal Particle Media (MP) | ||
Before I run scripts below I first mount both the source and the destination paths if necessary. Then the systax would be similar to the following. Of course the paths differ. (Important to add the last /.)
/home/…/scripts/rsync.WRAP <mount point> /<mount point>/<path>/
This first script, rsync.WRAP runs script rsync.PRJ.
*** Begin script rsync.WRAP ***
#!/bin/sh -x
cwd=`dirname $0`
if [ $# -lt 2 ] ; then
echo “USAGE: rsync.WRAP <SOURCE_PROJECT_NAME> <DEST_NFS_SERVER>”
exit
fi
SOURCE_PROJECT_NAME=`basename $1`
SOURCE_PROJECT_PATH=$1
DEST_NFS_SERVER=$2
[ -f /var/tmp/$SOURCE_PROJECT_NAME ] && rm /var/tmp/$SOURCE_PROJECT_NAME.*
[ -f /var/tmp/$SOURCE_PROJECT_NAME.tmp ] && rm /var/tmp/$SOURCE_PROJECT_NAME.tmp
cd $SOURCE_PROJECT_PATH ; find . -maxdepth 3 -type d \( -name .snapshot \) -prune -o -type d -print | cpio -pvdum $DEST_NFS_SERVER > /var/tmp/$SOURCE_PROJECT_NAME.tmp 2>&1
cat /var/tmp/$SOURCE_PROJECT_NAME.tmp | grep -v “^0 blocks” | sed -e “s,$DEST_NFS_SERVER/,,g” > /var/tmp/$SOURCE_PROJECT_NAME && rm /var/tmp/$SOURCE_PROJECT_NAME.tmp
cd /var/tmp ; split -l 20 $SOURCE_PROJECT_NAME $SOURCE_PROJECT_NAME.
for j in `ls -1 /var/tmp/$SOURCE_PROJECT_NAME.[a-z]*`; do
/home/thierse/files/professional/unix/scripts/rsync.PRJ $j $SOURCE_PROJECT_PATH $SOURCE_PROJECT_NAME $DEST_NFS_SERVER &
done
# Do a one time top level rsync to the project to get the files at top level
#rsync -lptgoDWSH –stats –exclude $SOURCE_PROJECT_PATH/.snapshot $SOURCE_PROJECT_PATH ${DEST_NFS_SERVER}::prj/$SOURCE_PROJECT_NAME
rsync -lptgoDWSH –stats –exclude $SOURCE_PROJECT_PATH/.snapshot $SOURCE_PROJECT_PATH ${DEST_NFS_SERVER}
*** End Script rsync.WRAP ***
*** Begin Script rsync.PRJ ***
This post is really just a cut and past from a netapp manual. I need to go through this information and write a post based on it that makes sense for using ssh in scripts to performs snapshots and snapvaults on netapp.
Public-key-based authentication
Setting up key-based authentication requires an RSA key pair (a private and public key) in addition to
the host and server keys. Public-key-based authentication differs between the two versions of SSH;
SSH 1.x uses an RSA key pair and SSH 2.0 uses a DSA key pair in addition to an RSA key pair. For
both versions of SSH, you must generate the key pairs and copy the public key to the storage system.
Next topics
Generating an RSA key pair for SSH 1.x on page 163
Generating key pairs for SSH 2.0 on page 164
Editing public keys generated by SecureCRT and ssh.com clients on page 165
Generating an RSA key pair for SSH 1.x
Public-key-based authentication using SSH 1.x requires an RSA key pair.
Steps
1. Using your SSH 1.x client, generate an RSA key pair.
Your client generates the RSA key pair, a public key and a private key, and stores them on the client.
2. Copy the generated public key to the storage system root volume and append it to the
/etc/sshd/user_name/.ssh/authorized_keys file.
Example generating an RSA key pair
The following is an example of generating an RSA key pair with an OpenSSH UNIX client:
% ssh-keygen -t rsa1 -b 1024
Generating public/private rsa1 key pair.
Enter file in which to save the key (/u/john/.ssh/identity):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /u/john/.ssh/identity
SecureAdmin | 163
Your public key has been saved in /u/john/.ssh/identity.pub
The key fingerprint is:
6a:c7:93:7c:b5:f4:12:87:81:56:5e:a2:62:40:07:8a john@unix1
In this example, the identity.pub file is the public-key file that you copy to the storage system
root volume.
The following commands append the public key to the
/etc/sshd/user_name/.ssh/authorized_keys file on storage system sys1:
% mount sys1:/ /mnt_sys1
% cat identity.pub >> /mnt_sys1/etc/sshd/john/.ssh/authorized_keys
Generating key pairs for SSH 2.0
Generating key pairs for SSH 2.0 requires generating an RSA key pair and a DSA key pair.
If you use SSH 2.0 clients other than OpenSSH, you might have to edit the public key before you can
use it.
Steps
1. Using your SSH 2.0 client, generate an RSA key pair.
Your client generates the RSA key pair, a public key and a private key, and stores them on the client.
2. Using your SSH 2.0 client, generate a DSA key pair.
Your client generates the DSA key pair, a public key and a private key, and stores them on the client.
3. Copy the generated public key to the storage system default directory and append it to the
/etc/sshd/user_name/.ssh/authorized_keys2 file.
Example generating RSA and DSA key pairs
The following is an example of generating RSA and DSA key pairs with an OpenSSH UNIX
client.
% ssh-keygen -t rsa -b 1024
Generating public/private rsa key pair.
Enter file in which to save the key (/u/john/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /u/john/.ssh/id_rsa
Your public key has been saved in /u/john/.ssh/id_rsa.pub
% ssh-keygen -t dsa -b 1024
Generating public/private dsa key pair.
Enter file in which to save the key (/u/john/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
164 | Data ONTAP 7.2 System Administration Guide
Enter same passphrase again:
Your identification has been saved in /u/john/.ssh/id_dsa
Your public key has been saved in /u/john/.ssh/id_dsa.pub
In this example, the id_rsa.pub and id_dsa.pub files are the public-key files that you copy
to the storage system root volume.
The following commands append the public keys to the
/etc/sshd/user_name/.ssh/authorized_keys2 file on storage system sys1:
% mount sys1:/ /mnt_sys1
% cat id_rsa.pub >> /mnt_sys1/etc/sshd/john/.ssh/authorized_keys2
% cat id_dsa.pub >> /mnt_sys1/etc/sshd/john/.ssh/authorized_keys2