I’ve liked the PGP brand since watching Zimmerman fight to keep PGP going in the early 1990s, when PGP met the standards of a non-exportable weapon. That is, until Zimmerman published a physical book with the source code in OCR-friendly font and ended up with PGP covered under the first ammendment. All of that is such old history though. Zimmerman has been gone since 2001, after a merger and then an acquisition by Network Associates. The company then ended up getting dumped by Network Associates and refounded (with assets bought back from Network Associates) with a little VC. It’s been a weird journey to get to where they are today. I hate to watch it go away (again) as a company though. Hopefully this acquisition will go better than things went when they were part of Network Associates.

Symantec is also acquiring GuardianEdge. GuardianEdge products already integrate nicely alongside the Symantec portfolio. You can even deploy GuardianEdge with a special Altiris Connector into Altiris Notification Server, which alerts you when systems “present risk to protected information”. Overall, either PGP or GuardianEdge seem like great adds to the Symantec lineup. Both from the outside seem a bit superfluous but I have to guess someone has a great strategy for integrating the two brands into one. I look forward to watching it unfold.Similar Articles:

• Symantec Continues to Beef Up SaaS Solution Offerings
• Mac OS X: tail
• Mac OS X for Unix Geeks
• Houseport Z-Wave for Mac Finally Available!!
• Lo/Jack

For example, the option to replicate between two of them. Most have NAS to NAS replication built in. However, that replication ends up being dependent on having two of them. But what if you just have a machine on the other side of the replication, want to back it up remotely compressed or want to back up to a cloud environment. Well, if it’s not the same daemon then you’re typically stuck with CIFS, NFS, HTTPS (WebDAV) or FTP. The devices don’t typically give you the option to push directly from it nor to run a daemon that non-proprietary device can connect to directly, so you’d have to use a client to do the offsite sync. One example of how to do this would be to use JungleDisk and an Amazon S3 account. JungleDisk would mount the AmazonS3 storage and the NAS storage (all share points). You would then use a tool such as ChronoSync, Retrospect (Duplicate scripts not backup scripts btw) or even rsync to backup the device over CIFS. It’s not pretty, it’s extra latency and management, but it would work.

The reason you would do synchronization is that if you attempt to backup (a la Retrospect Backup Scripts) then you’d send big, monolithic files over the wire. The smaller increments of data you can send over the wire the better. Another tool that can do that type of sync is File Replication Pro. That would actually do blocks instead of files, pushing an even smaller increment of data over the wire. There are certainly other services. You could even open up the firewall (for just the specific ports/IP addresses requiring connectivity, which is always a potential security risk) and have a remote backup service come in and pull the data sync over FTP, CIFS or WebDAV (if you want to stick with a cloud backup solution), but those types of services are a bit more difficult to find.

The same is pretty much the same for cloud based storage. With the exception that instead of a built-in feature you’re either looking for a built-in feature or an API that allows you to develop your own. The moral of this story, if you use a NAS or a cloud-based solution and you want to back your data up, then your options are limited. Keep this in mind when you decide to purchase a NAS rather than, let’s say, a Mac OS X Server running on a Mac Mini with some Direct Attached Storage (DAS) connected to it.Similar Articles:

• Xsan TCO
• Looking at Amazon's Cloud
• Mac in the Cloud
• Final Cut Server: Using Amazon S3 for Archival
• Using Microsoft Document Connection on a Mac

• iPhone Skin
• Advanced iPhone Development
• iPhone in the Enterprise
• RSA Makes a Case for iPhone in the Enterprise
• iPhone and Address Bar Icons

• Whoami lists the user you are currently logged in as from the command line.
• Who lists the users logged onto your system.
• Id shows a list of all defined users and groups whether they are actually logged in.
• Groups <userid> shows a list of all the groups a user is in.
• Whois lists ownership information for domains.
• Hostname lists the name of the computer you are currently working on. You can also use hostname to set the name of the computer.
• Ifconfig is used to show you information about your network adapter.
• Dig is a utility for interrogating DNS servers. It is used to ask a DNS server for a type of record and provide the information for the DNS server.
• Netstat is a highly configurable tool that can show you the status of your network interfaces. This can help administrators break down which IP addresses are connecting to servers, the name of the system using the IP address, and the ports users are accessing the server over.
• Ping sends a request to a system. If the system supports the ability to respond, then the system will do so. Ping can be used to check the availability of a system and make sure data can reliably make it to the system being pinged.
• Traceroute is a utility for tracing where data goes through the Internet to get to a specified destination. The traceroute command is useful when troubleshooting connectivity issues between two locations.

Similar Articles:

• The Cut, Copy & Paste Daemon in OS X
• Xsan + serialnumberd Troubleshooting
• Xsan: Stripe Group Down Errors
• NetWare + Portlock

• Cisco + Postpath = Unified Communications – Clear Strategy
• Fireplotter
• The Changing Mac Switching Infrastructure
• WAN Acceleration Magic Quadrant
• Partner Programs

• dhcp_time_offset (option 2)
• dhcp_router (option 3)
• dhcp_domain_name_server (option 6)
• dhcp_domain_name (option 15)
• dhcp_network_time_protocol_servers (option 42)
• dhcp_nb_over_tcpip_name_server (option 44)
• dhcp_nb__over_tcpip_dgram_dist_server (option 45)
• dhcp_nb_over_tcpip_node_type (option 46)
• dhcp_nb_over_tcpip_scope (option 47)
• dhcp_smtp_server (option 69)
• dhcp_pop3_server (option 70)
• dhcp_nntp_server (option 71)
• dhcp_ldap_url (option 95)
• dhcp_netinfo_server_address (option 112)
• dhcp_netinfo_server_tag (option 113)
• dhcp_url (option 114)
• dhcp_domain_search (option 119)
• dhcp_proxy_auto_discovery_url (option 252)

But you can also add options by their numerical identifier. To add them, add the following into your /etc/bootpd.plist file and then restart the DHCP service:

<string>dhcp_option_120</string>

<data>

192.168.210.7

</data>

Similar Articles:

• Mac OS X Server and WINS
• Mac OS X Server: Installing the OS
• Adding Recursion in named.conf
• Mac OS X Server 10.5: Introduction to RADIUS
• Mac OS X Server 10.5: Advanced Mode

There have been a number of concerns about security with regards to cloud services. The ability to build a dynamic tunnel between your AWS assets and your organization is now here. It’s interesting to see the price of security so simply laid out like that. Now how to factor risk versus just using otherwise encrypted protocols to communicate back to the office? Calculating risk with regards to data security is a pretty complicated task to those of us without CISSP+RMPhD (CISSPs and PhDs in Risk Management)…Similar Articles:

• A Saturated Cloud Backup Market
• Meet the Press
• Amazon AuthorCentral
• Final Cut Server: Using Amazon S3 for Archival
• Updated Amazon Author Page

Similar Articles:

• Snow Leopard + SkyHook = Kerb Problems?
• WiMax Enabled Laptops
• On the Road: Sprint SmartView

To use the s3 script, you need to store your Amazon secret key in a text file and set two environment variables. The INSTALL file included with the package has all the details. The only tricky part I ran into, and from the comments on Amazon, other people ran into, is how to create the secret key text file. Now go into your environment variables in ~/.bash_profile and add S3_ACCESS_KEY_ID (your S3 access key id) from the S3 site on Amazon Web Service and S3_SECRET_ACCESS_KEY (the name of the file with your S3 secret key). If the file that stores this key is called ~/SUPERSECRET then to create it, copy the key to your clipboard from the AWS site and then run echo -n and send the contents of the pasted line to a file:

echo -n MYPASTEDKEY > ~/SUPERSECRET

The -n switch tells echo to not include a new line character and results in a text file of exactly 40 bytes. Once I got the key file created correctly, the s3 script started working, and I was able to upload, download, and list objects in S3.

Next, we’ll list your buckets:

s3 buckets

Then we’ll list the contents of a bucket called images:

s3 list images

Next, we’ll upload a file called emerald.png from the desktop of our computer:

s3 put images emerald.png ~/Desktop/emerald.png

Now let’s try and get the same file and just leave it somewhere else so we can compare the two:

s3 get images emerald.png ~/Documents/emerald.png

Now let’s get rid of the file:

s3  rm images emerald.png

And then to just remove all the files from the bucket:

rmrf images

If you notice, this toolkit is very similar to the s3cmd kit that we looked at earlier.  It’s a little more limited, but I thought it might come with less of a learning curve or be easier to script against depending on what you need.Similar Articles:

• Mail Attachments from the Command Line
• Deploy EC2 En Masse
• Custom VMs using S3+EC2
• Scripting Productions and Assets in Final Cut Server
• Shell to Clipboard & Back Again

There are a number of tools that have been developed by the community to leverage Amazon’s S3 Storage Service.  This isn’t as cut and dry as using ec2 due to the fact that the Amazon tools are written in Java, C#, Perl, PHP, Ruby and Python.  However, I’m a shell kinda’ guy to a large degree and I was able to find a couple of places where people have written shell wrappers for the tools made available by Amazon. The first is called s3cmd, which we will cover in this article and the second is called Another S3 Bash Interface, which we will cover in a future article.  The following assumes that you have already setup an account with Amazon Web Services (AWS).  As for terms, bucket is the big one: think of a bucket like a logical partition of your s3 account, similar to a volume (I say as I duck so that when someone throws something at me for oversimplifying they hopefully miss).

s3cmd is pretty straight forward to use. Download it from the developer’s site (linked to from above) and then run through the setup wizard using the following:
s3cmd –configure

For most future commands, you’ll notice that there will be a path that shows s3:// as part of the URL/URI; this is because s3cmd uses the s3:// to reference the root of your s3 account.  Now that you’ve configured s3cmd let’s go ahead and make a new bucket called server01_backup, which can be done using the mb verb:

s3cmd mb s3://server01_backup

Now that we have a bucket, use the ls verb of the s3cmd to list your available buckets:

s3cmd ls

Once you’ve verified that you have a bucket, let’s look at the contents of the bucket:

s3cmd ls s3://server01_backup

Now let’s copy a file into a bucket, which we’ll do using the put verb followed by the source and then the path:

s3cmd put /Volumes/Backup/backup.tar s3://server01_backup/backup.tar

Now let’s go ahead and create another bucket for web images called images:

servercmd mb s3://images

Once we have a bucket for our web images, let’s upload a file to it:

s3cmd put –acl-public –guess-mime-type ~/Desktop/emerald.png s3://images/emerald.png

Because we used the –acl-public flag with the put verb the file is now available by anyone in read only form.  The output of the command will have a line that indicates the URL that can then be used to access the file later, as can be seen here:

Public URL of the object is: http://images.s3.amazonaws.com/emerald.png

You can now call on the file as you would any other file, using the path.  If you saw the previous article on leveraging s3 with Final Cut Server then you’ll likely be interested in the fact that this can be automated through the scripts option of Final Cut Server.

Next, let’s say that you wanted to copy a nested directories contents into your images bucket, you’d use the the put verb with the –recursive option, then list the source and finally the target:

s3cmd put –recursive images s3://images/

Let’s say that we’re now done with our images bucket and ready to delete it.  This can be done using the rb verb with s3cmd, which standards for “remove bucket.”

s3cmd rb s3://images

s3cmd also has an option to synchronize, making it a pretty darn nice offsite replication solution.  Let’s say you’re keeping a website on your local drive and want to sync it to Amazon nightly, just add the following to a cron job:

s3cmd sync  ./  s3://DocumentRoot/

If you’re going to use sync with a fairly well built out directory structure, also consider using the –dry-run flag for a little sanity checking before you go synchronizing a lot of data.  You can also use the -include and -exclude flags to limit what s3cmd will synchronize.Similar Articles:

None Found