Archive for ‘Backup & Restore’

July 4, 2011

Cloud Client Computing

Client cloud computing offers lot of benefits to the organisation. Energy efficient (Green IT), up to date, more reliable, access anywhere, portable, mobility, cost effective, easy to deploy, easy to re-store, less management and maintenance. Client computing challenges are handled by cloud client computing.  To maintain client systems, every organisations spending good amount money. Engineers required all the sites. These challenges handled by cloud. In this category I can recommend a product Wyse.

Cloud Client Computing

Cloud Client Computing

Wyse Cloud Client Portfolio

  1. Wyse Cloud Clients
    • Wyse Thin Clients – Sophisticated. Secure. Friendly. Performance with flexible functionality.
    • Wyse Zero Clients – Simple. Secure. Stingy. Performance with dedicated functionality.
    • Cloud PCs – Familiar. Performance. Improved. The PC, only better – with centralized OS, applications, and content.
  2. Handhelds – Complete support for Apple iOS and Google Android smartphones and tablets viaWyse PocketCloud, the leading Mobile Cloud Software for enterprises and consumers.
  3. Wyse Ultra-thin Firmware – Wyse ThinOSLinuxWindows CE and Windows Embedded Standard– the most comprehensive, secure, scalable and reliable cloud client firmware suite in the industry.

Wyse Cloud Software Portfolio

  1. Wyse Cloud Client Software
    • Wyse Zero™ – Cloud-based technology engine powering a new world of cloud-connected dedicated Zero Clients.
    • Wyse Mobile Cloud Software – Wyse PocketCloud, the leading cloud-based mobile app suite connecting you to your personal, private or public cloud from any handheld.
    • Wyse Cloud PC Software – Cloud-based software to cloudify your PCs, TCs, or VMs by centralizing their OS, apps and content in a private cloud.
  2. Wyse Management Software – Secure. Scalable. Cloud-centric remote device management for the extended enterprise.
  3. Wyse Virtualization Software – Delivering the best user experience and optimized performance for any cloud client deployment.

June 12, 2011

Riverbed Whitewater™ and Steelhead™, – Cloud Data Protection for Backup, Archive, and Disaster Recovery

Riverbed Cloud Service products, Whitewater™ and Steelhead™, enable organizations to improve their data protection and disaster recovery strategies quickly and easily. The Riverbed Whitewater™ appliance enables organizations to increase their data protection and disaster recovery strategies by moving backup data directly into cloud storage. Organizations looking to leverage cloud storage will be able to deploy Whitewater without any changes to their existing backup processes or products. Moreover, backups moved into the cloud will be de duplicated in-line, reducing overall bandwidth and cloud storage requirements, and the data will be secured at rest, as well as in flight to the cloud, making cloud storage, cloud backup, and cloud archive an integral part of an organization’s data protection strategy.

Key Whitewater Benefits:

  • Reduce disaster recover costs with cloud data protection
  • Meet accelerated recovery SLAs
  • Simplify off-site data storage for DR
  • Secure offsite data
  • Deploy with no change to existing backup infrastructure


Cloud Steelhead™

Cloud Steelhead™ offers the same WAN optimization functionality you’ve come to know and trust, in a form factor that’s much better suited for public cloud environments. It completely interoperates with Steelhead® appliances, Virtual Steelhead™, and Steelhead Mobile™ clients.

Cloud Steelhead includes tools that allow for instant deployment and easy cloning of instances. It also has a uniquely advanced model for intercepting traffic in the cloud. In addition, a new portal allows for easy management and licensing, and instant upgrades of cloud Steelhead instances.

Key benefits of Cloud Steelhead:

  • Instant deployment
  • Simple, portal-based management
  • Elastic sizing and easy cloning
  • Advanced cloud interception
  • Cloud-like pricing model

March 3, 2011

Security Threats In VoIP

Users have been exposed to the risks of sending data over the Internet while at the same time having the expectation that telephone conversations are strictly confidential. Security issues in the data and voice networks are in fact very similar, but completely separate in the minds of most users. Major security concerns of VOIP networks.

• Phreaking
Phreaking is a slang term coined to describe the activity of a subculture of people who study, experiment with, or explore telecommunication systems. This is sometimes called the H/P culture (with H standing for hacking and P standing for phreaking). Through this making calls through another user network, putting cost to that person.
• Eavesdropping
Eavesdropping is how most hackers steal credentials and get important information like business data. Through eavesdropping, a third party can obtain names, password and phone numbers, allowing them to gain control over voicemail, calling plan, call forwarding and billing information.
• Vishing
Vishing is a party calling you faking a trustworthy organization (e.g. your bank) and requesting confidential and often critical information.
• DoS (Denial of Service)
DoS attacks can be carried out by flooding a target with unnecessary SIP call-signaling messages, thereby degrading the service.
• SPIT (Spamming over Internet Telephony)
SPIT attacks consist of sending a voicemail to a person, masquerading it with information from a party trustworthy to the receiver, like a bank or online paying service, making him think he is safe.
• Man-in-the-middle attacks
VoIP is particularly vulnerable to man-in-the-middle attacks, in which the attacker intercepts call-signaling SIP message traffic and masquerades as the calling party to the called party, or vice versa. Once the attacker has gained this position, he can hijack calls via a redirection server.

December 23, 2010

Cloud Infrastructure

I was reading through the could infrastructure. It’s going to change the way we work with infrastructure. For me as an infrastructure professional it’s change the environment. Very easy to build the systems. Easy access, easy disconnection and lot more change the way we manage.

My end user desk tops are from cloud. My server’s and application’s are from cloud. I will be keeping a big pipe WAN link, dump terminals, telephones, and LAN connections of these. The entire infrastructure is from cloud. Applications are browser based. All the applications are accessed through an integrated area or form a portal. All the infrastructure is managed cloud provider. Locally no server, no data, no application. More and more mobile workers. Good to see more……

Cloud Infrastructure

July 5, 2009

Disaster Recovery

Disaster recovery planning is a subset of a larger process known as business continuity planning and should include applications, data, hardware, communications (such as networking) and other IT infrastructure. A business continuity plan (BCP) includes planning for non-IT related aspects such as key personnel, facilities, crisis communication and reputation protection, and should refer to the disaster recovery plan (DRP) for IT related infrastructure recovery / continuity.

General steps to follow while creating BCP/DRP

  1. Identify the scope and boundaries of business continuity plan. First step enables us to define scope of BCP. It provides an idea for limitations and boundaries of plan. It also includes audit and risk analysis reports for institution’s assets.
  2. Conduct a business impact analysis (BIA). Business impact analysis is study and assessment of financial losses to institution resulting from destructive event as unavailability of important business services.
  3. Sell the concept of BCP to upper management and obtain organizational and financial commitment. Convincing senior management to approve BCP/DRP is key task. It is very important for security professional to get approval for plan from upper management to bring it to effect.
  4. Each department will need to understand its role in plan and support to maintain it. In case of disaster, each department has to be prepared for the action. To recover and to protect the critical systems each department has to understand the plan follows it accordingly. It is also important to maintain and help in creation of plan for each individual department.
  5. The BCP project team must implement the plan. After approval from upper management plan should be maintained and implemented. Implementation team should follow the guidelines procedures in plan.
  6. NIST tool set can be used for doing BCP. National Institute of standards and Technologies has published tools which can help in creating BCP.


Acronis, Inc. is a company incorporated in Delaware that produces hard disk utility software, including disk-imaging backup and recovery, partition management, and boot management software. It also develops software for virtualization migration and conversion, for the purpose of migrating a physical server to a virtual server (such as VMware), or what is also termed P2V. Its best-known product, Acronis True Image, creates a software image of a computer disk in order to restore an exact image on the same or another computer. Most software is produced in different versions, from low-priced software for single computers up to versions for companies with many desktop and server computers.

Reference: Wikipedia

June 22, 2009

Drive Offline in NetBackup

The drive will go offline in NetBackup frequently, due to the proper driver installation. This is one of the reasons of drive going offline. We have to install the Symantec Device Driver.

Symantec Device Drivers for Veritas NetBackup ™ Windows Servers –

June 15, 2009

Backup Administrator – Backup Tracking Log

Tracking and monitoring of backup one of the major challenges of the organization. It needs to be done with more cautious and very serious. There are couple ways we can build a tracking log and maintain. The tracking sheet is very vital for Backup Administrator. This is required in the following scenarios:-

  1. Plan the backup window
  2. Plan the tape requirement
  3. Plan the storage requirement, if it’s taking to disk or staging to disk
  4. Analyze the data growth
  5. Plan about ILM (Information Lifecycle Management)
  6. To retrieve data
  7. Track backup failures
  8. Time required for each backup and retrieval
  9. Plan ad hoc backups
  10. Retention analysis

Sample Log Sheet.