Yes. It is possible. Here is the official documentation.

You can take the backup to local drive and then move it to the network drive. With you can minimize the risk of having corrupt backup files

Here is one which explains Memory counters

sp_helprevlogin does it well. Have a look at this.

You may use perfmon to find out which process is accessing that file. An example here[/url]

You may find this article useful.

Try doing a CHECKDB on master

Backups are never an overhead for a DBA! Explore the various options available in SSMS/Maintenance Plans to handle backups and clean up.

You will select "Add node to.....". Please refer http://www.mssqltips.com/tip.asp?tip=1721

Small tweak to Oliiii's query will give the object name as well

Select object_name(object_id), STATS_DATE(object_id, stats_id) LastUpdate From sys.stats

I second Steve. It is not a good practice to copy the data files manually when the database is operational. There are be many unpleasant surprises later on. Best option...

This article has good explanation on TDE

Check if the SQL Server service account has privileges to the following registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Providers

Do a RESTORE HEADERONLY on the backup file. It should tell you whether the backup set is complete. If you see "INCOMPLETE" in the output, the backup file is bad

Yes. You need to run setup.exe on both the nodes.