Disaster Recovery/Fail-Over in 1.5 hr form start to finish:
Situation: A Client in RTP experienced a total loss of power in their building around 6AM due to snow storm. Utility company did not have an ETA for power restore. Client called Avaria to fail-over servers in Disaster Recovery Mode.
8:25AM: Client called Avaria to go into Disaster Recovery mode. Avaria maintains and manages a 24x7x365 server replication setup between its datacenter and Client’s office.
9:05AM: Avaria brought the replicated file server online (1.5 TB data) at its datacenter in about 10 minutes.
9:25AM: After testing routing and DNS services, Avaria’s network admin confirmed server was fully functional, accessible and usable at Avaria’s datacenter.
Client confirmed all services were running and data was now accessible from Client’s office and to employees from home.
Client’s President/CEO: 1:46PM: “Thanks for the back-up planning and Disaster Recovery execution today... Well done!" - Specialty Insurance
Custom Server Deployment
Situation: 10:26am (deep into Labor Day weekend): Client requests a new server to be deployed immediately to replace a server that was deployed on an hour’s notice just two days ago.
Why? Because Client’s application developer had mistakenly requested wrong operating system and wrong SQL version.
11:55am: Avaria’s account manager responded via email “I'll try my best to line up a resource and get this going in the next few hours.”
12:50PM: Avaria lined up resources and started the deployment.
2:350PM: Client’s new server had been fully provisioned, 138 updates applied, remote access enabled in support portal and granted, credentials sent to Client’s developer.
3:13pm: Client responds “Many many thanks and apologize for the holiday interruption”.
- Education App Developer
Benefits of Virtualization
Situation: 11:05am: Client’s end users had been complaining that applications on their server were running too slow.
11:11am Technician determined the server needed more CPU power.
11:14am Sent an email to the Client saying that he could remotely add another CPU to their server and their downtime would be about 10 minutes. Client responded saying he could upgrade during their lunch break.
12:10pm technician upgraded server. Downtime: 7 minutes, and no complaints since then. - Medical Practice
Custom FTP Server Setup
8:05am: Client called saying their billing vendor needed reports uploaded to the vendor’s network.
10:15am Technician setup a secure FTP server, allocated credentials, tested connectivity and access.
12:45pm contacted the vendor and remotely trained vendor’s staff how to view files. 100% work performed remotely.
- Medical Practice
Typical Same Day Physical-to-Virtual Server Conversion
Situation: Client’s server was 5 years old and was costing 10 to 15 hours of monthly maintenance costs and frequent downtime. Client agreed to get rid of the server and go with a virtualized server instead of buying new hardware. Friday was a good day because Client’s office closed early.
12:20pm Technician backed up the server using imaging software, transported the image to the datacenter and loaded the image into our virtualized environment.
4:43pm called the client asking to test remote access, test software and applications and make sure all data looked good.
6:07PM Client emailed saying “all looks great”. - Medical Practice
Early Morning (ISP’s) Issue
7:26am Client reported “no Internet, no phones” in their office.
7:34am Technician asked for their Time Warner account information.
7:48am Technician was on the phone with TWTC; determined problem was at TWTC’s connection outside Client building. Worked with TWTC’s engineer troubleshooting their equipment.
8:20am Outside connection was up. Remotely tested Client firewall and Internet router. Determined all was looking good.
8:35am informed the Client they were back up and running. - Service Franchise
Stale DNS Records; ISP issue
Sunday 1:33pm: Client’s CFO reported that she could not login their server from home.
1:35pm Technician tested access to the server and confirmed that the problem was at Client’s home Internet connection. Walked the Client over the phone through testing and troubleshooting home Internet connection.
1:57pm finished up the task by clearing out stale cached DNS records and Client was able to login the server by texting back “That worked”. - Services Company
Proactive Alerting Saves the Day
7:47am: Avaria’s monitoring system alerted a key server at Client site was down due to power outage. Client’s office was not yet open.
7:56am Contacted the Client informing that we needed Client to power cycle the server.
8:14am Client had just gotten to the office; turned on the server.
Avaria’s tech tested connectivity and critical services (DNS, DHCP, print services). All looked good. 8:26am Informed the Client all looked good.
Client’s office starts at 8:30am sharp. - Services Company