Procedures

Here are procedures to be followed by Support Staff in respect to various technical matters in day to day operations of client issues.

NEOSYS Support Policies

In order to maintain good payment speed by clients NEOSYS needs to restrict support to clients that dont pay their bills on time, however the degree of restriction needs to depend on an intimate knowledge of the client which cannot be expected from all NEOSYS support staff. Therefore we will use a simple escalation policy as follows:

NEOSYS SUPPORT MANAGERS WILL maintain an overdue/stop list on a whiteboard visible to all support staff. Generally clients will go on the list when their invoice is seven days overdue and come off only after satisfactory commitment to pay have been obtained.

NEOSYS SUPPORT STAFF WILL discretely refer any calls for support from client on the overdue/stop list to support managers for handling.

This policy excludes:

1. Contacting the client to change the USB disk on the scheduled day, in case they haven't done so by 12 pm
2. Contacting the client or if the client contacts support staff regarding backup failures and to take measures to fix these failures

Handling client issues

Handling error messages

1. The very first step is understanding client problem.
2. Ask the client what error does he gets on the screen.
3. If error seems to be familiar then resolve it over the phone.
4. If error is unknown then ask user to send a screenshot of the error displayed along with the options used (basically you need to know HOW to replicate the error)
5. Upon receipt of the error, check in all the wikis for a solution.
6. If the issue is unknown or you don’t understand it clearly ask the user then use remote support to gain access to the users desktop to view how to replicate the error.

If it is new issue then report by escalation the same issue to your manager with a brief explanation.

Handling problems with report totals

Questions with regards to report totals should not be escalated to the programmers without following this procedure. If the total can be be broken down into items (as they nearly always can be in NEOSYS) then only a problem where the items dont add up to a total should be escalated, since that would be a system error.

Backup Procedures

Preparing daily backup report

1. Note the success, failure and other error of the clients backup mail in an excel sheet and forward the same to your manager.
2. If there is a backup failure or backup is not available, check wiki to take necessary steps.
3. If there is any unknown error, forward the same to your manager.

Updating Nagios incase of failures

1. If the backup failure is unsolved, schedule downtime Neosys service in Nagios till 01 am.
2. If the backup did not happen because of server down. Call the IT person; ask him to re-boot the server and check wiki to do necessary step ahead and schedule downtime to Nagios for 2hours.
3. If there is an error "Backup->Impossible" on Nagios check wiki and schedule downtime to Nagios for 2hours.

Interchange backup USB mail reminder

1. Basically all the clients have different days to change their backup USB. All the notification can be seen on Nagios at 12.00 pm every day.
2. When you see the change backup notification on Nagios at 12.00 pm, send a mail to the IT person or the person who changes the USB. As you send the mail schedule downtime for Neosys services for two hours.
3. Check the Nagios at 2.00 pm if the backup USB is changed, don't send another mail and stop there. But if backup is still not yet changed, send a another mail and this time cc the mail to your manager. After sending the mail, schedule downtime for Neosys service for more two hours.
4. Now at 4.00 pm if you still find the backup USB not changed. Call the IT person and ask him to change the USB ASAP and schedule downtime for Neosys services for one hour.
5. Now at 5.00 pm check Nagios and see if the backup USB is changed and if not changed. Send the mail to everyone from the backup mail.
6. If the backup is still not changed, escalate the issue to your manager.

Finding out which USB is inserted into the server

As we ask the client to have 3 USB's and interchange them weekly, we also need to sometimes track which one of these 3 USB's are inserted into the server. USB's can be tracked using their volume serial number in most cases. To find this out either go to the command prompt and type VOL or in the nightly backup message check for the 2nd line (which looks like this - 14/12/2009 2:45pm Media: 705B-5B5F). However serial numbers can be the same even for different USB's.

Creating and Handling passwords

Creating a password

Passwords are generated from a pass phrase and it is important to create a very difficult to guess pass phrase.

For example, a good pass phrase would be: Today is a good day and it is the best time to go for a holiday

The password for this would be Tiagdaiitbt2g4ah

The important instructions for the above are:

1. You have to take the first letter of each word and that makes your password (i.e. by using initials)
2. Wherever any word starts with a capital, then you have to take first letter as a capital (eg. For Today you will take T)
3. Replace and with &
4. Replace to with 2
5. Replace for with 4

Handling passwords

1. Never send the actual password - always send the pass phrase
2. Make sure that the password created out of the pass phrase is at least 10 characters long since using initials results in a lot of i's and a's etc which reduces the effectiveness of the password and allows hacking via brute force guessing especially since windows doesnt slow down logins even if it sees thousands of password attempts
3. Pass phrases are never to be sent by email, whatever the case maybe.
4. Pass phrases can be sent by chat - however they have to be broken down in two parts and sent separately over two different messengers or if you are using Gtalk then use the 'off the record' mode.
5. Using SMS to send pass phrases is the best known way as of now.
6. If you save the passwords on your system as a file, make sure the file is encrypted with a master password.