Backup Exec for Windows Servers includes support for a wide
array of robotic libraries (also referred to as an autoloader or changer) and
tape drives. Prior to proceeding with the rest of this document, confirm that
the tape hardware is listed on the Hardware Compatibility List (HCL) for the
version of Backup Exec which is installed per the following
link:
http://www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=15047
Note: Tape Hardware which is not listed on the HCL may be detected by or function with Backup Exec, but may not have been tested and is not officially supported by Symantec.
Occasionally, hardware which has been officially tested and is supported by Symantec may not be displayed or may appear offline in the Backup Exec Interface (i.e.: Devices Tab), may not function correctly, or may report specific errors in the job log or Windows Event Viewer Log. This document has several suggestions on how to potentially resolve these issues.
Please note: Some hardware manufacturers may have implementation and troubleshooting documentation available that have more detailed information for particular device than what is listed below. The following are examples of this:
HP StorageWorks Enterprise Backup Solution with Symantec Backup Exec implementation guide
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00097075/c00097075.pdf
Please make sure to review the hardware manufacturer's documentation and if there are still issues after doing so and performing the steps below, open a support case with the hardware manufacturer to confirm that the tape hardware is functioning properly.
Basic Configuration and Troubleshooting Procedures:
I. Verify the hardware is detected properly by the Operating System and not being managed by another third party application
a. Open the Device Manager in Windows and verify the hardware is present. Verify the controller, tape drive(s), and robotic library (if applicable, will need to show as an Unknown Medium Changer) are present in Windows Device Manager:
II. Verify Robotic Library Support is enabled and the latest Backup Exec Tape Device Drivers have been installed
a. In the Backup Exec console click on Tools > Serial Numbers and Installation. In the installation wizard go past the serial numbers screen and verify that the Enable Robotic Library Support option is selected and installed.
If the option is not selected, select the option and proceed with the installation.
c. Verify that the autoloader's media management is set to Random.
Advanced Troubleshooting Procedures:
V. Verify the device configuration is supported by Backup Exec
VII. Orphaned Devices in Windows Device Manager and/or devices no longer detected or offline in Backup Exec
Please see the following document for how to check for orphaned devices in Windows Device Manager:
How to remove old tape drivers from Windows that are no longer needed or in use.
http://support.veritas.com/docs/308914
It is quite possible that an orphaned devices may be present in Device Manager, especially after replacing hardware, or performing a firmware or driver update. Verify that there are no orphaned tape drives, medium changers, or controllers.
Remove any orphaned device(s) to eliminate any potential conflict.
VIII. Disable, delete and re-enable the device in Backup Exec
From the devices tab in Backup Exec, right-click the device and select Enable. This should remove the check mark next to the device and disable it. After disabling the device, right-click the device again, this time choosing delete.
After deleting the device(s), stop the Backup Exec services. With the services stopped, run Tapeinst.exe from x:\Program Files\Symantec\Backup Exec\. Choose the following options (Figure 8):
Tracer.exe should also be running at this time as indicated in step #4 to review for any SCSI errors. Restart the Backup Exec services, and see if the devices are detected properly.
IX. Verify that the Device and Media Service is running under a Domain Admin account and/or built-in Administrator Account
If the media server is part of a domain, the Backup Exec Device and Media Service, in addition to all the Backup Exec Services (except the Remote Agent Service) should be using an account with Domain Admin privileges and/or built in Administrator Rights. Please see the Backup Exec Administrator's Guide for further information regarding the required rights for the Backup Exec services account.
For additional troubleshooting information, please refer to the TechNotes in the Related Documents Section below.
Related Documents:http://www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=15047
Note: Tape Hardware which is not listed on the HCL may be detected by or function with Backup Exec, but may not have been tested and is not officially supported by Symantec.
Occasionally, hardware which has been officially tested and is supported by Symantec may not be displayed or may appear offline in the Backup Exec Interface (i.e.: Devices Tab), may not function correctly, or may report specific errors in the job log or Windows Event Viewer Log. This document has several suggestions on how to potentially resolve these issues.
Please note: Some hardware manufacturers may have implementation and troubleshooting documentation available that have more detailed information for particular device than what is listed below. The following are examples of this:
HP StorageWorks Enterprise Backup Solution with Symantec Backup Exec implementation guide
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00097075/c00097075.pdf
Dell
Solution Network: Step-by-Step Troubleshooting Wizard for Tape Drives
Please make sure to review the hardware manufacturer's documentation and if there are still issues after doing so and performing the steps below, open a support case with the hardware manufacturer to confirm that the tape hardware is functioning properly.
Basic Configuration and Troubleshooting Procedures:
I. Verify the hardware is detected properly by the Operating System and not being managed by another third party application
a. Open the Device Manager in Windows and verify the hardware is present. Verify the controller, tape drive(s), and robotic library (if applicable, will need to show as an Unknown Medium Changer) are present in Windows Device Manager:
In Windows 2003, right
click My Computer and choose Manage. From the Computer
Management snap-in, click on Device Manager (Figure 1).
Figure 1
In Windows 2008,
right-click Computer and choose Manage. From the Server
Management snap-in, expand Diagnostics and click on Device Manager
(Figure 2).
Figure 2
b. Confirm that
the Removable Storage Management (<RSM>) service is stopped
and disabled. If a Removable Storage Service Error (RSM cannot manage
library or tape device. The database is corrupt.) shows afterward in the System
Event Viewer Log, this error can usually be ignored and will stop occurring
after one or more reboots of the server have been performed.
c. Check the
installed programs in the Windows Control Panel, Add/Remove Programs
Applet. If there are any other third party backup applications, tape
tools, etc... un-install them. Backup Exec may not be able properly
communicate with tape hardware if another vendor's backup application is
installed, even if the services for that application are disabled. Tape
Diagnostic Tools should only be installed to test the tape hardware when the
Backup Exec Services are not running and then should be removed once the
diagnostic tests have been completed.
II. Verify Robotic Library Support is enabled and the latest Backup Exec Tape Device Drivers have been installed
a. In the Backup Exec console click on Tools > Serial Numbers and Installation. In the installation wizard go past the serial numbers screen and verify that the Enable Robotic Library Support option is selected and installed.
If the option is not selected, select the option and proceed with the installation.
b. Ensure that the latest drivers and firmware have been
installed for the tape drive, robotic library, and for the SCSI controller.
Symantec drivers should be loaded for the tape drive for best performance.
Symantec does not test performance or compatibility with Original Equipment
Manufacturer (OEM) drivers, unless noted on the Hardware Compatibility List.
Backup Exec tape drivers can be downloaded from the Symantec Support Web site
at: http://www.symantec.com/business/support/downloads.jsp?pid=15047
Select the appropriate Backup Exec version number in the
Product Version drop-down box, and select Driver as the File Type. Contact the
hardware manufacturer for the latest firmware for the robotic library, tape
drive, and SCSI controller. To verify that the Symantec Drivers have been loaded
for the tape drive, return to Device Manager in Windows and open the properties
of the Tape Drive. Verify that the Driver Provider is Symantec.
III. Confirm the tape hardware is properly configured, powered on, detected, & initialized prior to the Windows Operating System booting up
a. If the tape hardware is external to the server, power down the robotic library, tape drive, and server.
III. Confirm the tape hardware is properly configured, powered on, detected, & initialized prior to the Windows Operating System booting up
a. If the tape hardware is external to the server, power down the robotic library, tape drive, and server.
b. Verify that the device is configured to use the
proper addressing scheme.
For robotic libraries, verify
that the addressing scheme is set properly between the drives and the robotic
library:
- SCSI ID. If the library and/or drives support SCSI ID addressing, then verify that the library has a lower SCSI ID than the tape drives.
- Multi-LUN. If the library and/or drives support Multi-LUN addressing, then verify that the drives have a lower LUN number than the library.
For more information on
verifying the addressing scheme for the hardware, see the Related Documents or
consult your hardware documentation.
c. Verify that the autoloader's media management is set to Random.
- If the library is detected, but there are issues with moving or managing media, verify that the library is in Random and not Sequential or Stacker mode. Consult the hardware documentation for configuring this setting
d. Power on the robotic library and/or tape drive. Once the
autoloader or tape drive has fully initialized, power the server back
on.
Note 1: Anytime Backup Exec goes from being to able to properly detect or communicate with externally connected tape hardware to not being able to manage it, the procedure above should be repeated. Even if the Windows Device Manager detects the hardware after hard reboots, warm reboots, or because the library is disconnected or the power is cycled to the device, Backup Exec still may have communication issues with it. It is also recommended that the tape hardware be plugged into a backup power supply with surge suppression, just as the server or workstation it is connected to should be.
Note 2: Additional power on procedure steps may be required for tape hardware which is in a SAN (Storage Area Network) Environment because of switch, bridge, etc... equipment which is also involved.
Note 3: If the tape drive, medium changer, or controller is listed with an error or is not listed in Device Manager after performing the steps listed above, then consult the hardware documentation to verify the hardware is connected/terminated to the server properly. Verify also the controller can detect the device properly POST Bios Screen on boot-up and by booting into the controller BIOS. For further support contact the hardware vendor.
IV. Review the System Event Logs for hardware errors.
While in the Computer Management or the Server Management console, review the System Event Logs and see if there are any hardware errors being reported from the tape drive, robotic library, or controller cards. This is recommended even if the tape hardware is detected by Backup Exec/Windows and appears to be functioning properly.
The following are examples of hardware errors that might be present in the System Event Logs:
Note 1: Anytime Backup Exec goes from being to able to properly detect or communicate with externally connected tape hardware to not being able to manage it, the procedure above should be repeated. Even if the Windows Device Manager detects the hardware after hard reboots, warm reboots, or because the library is disconnected or the power is cycled to the device, Backup Exec still may have communication issues with it. It is also recommended that the tape hardware be plugged into a backup power supply with surge suppression, just as the server or workstation it is connected to should be.
Note 2: Additional power on procedure steps may be required for tape hardware which is in a SAN (Storage Area Network) Environment because of switch, bridge, etc... equipment which is also involved.
Note 3: If the tape drive, medium changer, or controller is listed with an error or is not listed in Device Manager after performing the steps listed above, then consult the hardware documentation to verify the hardware is connected/terminated to the server properly. Verify also the controller can detect the device properly POST Bios Screen on boot-up and by booting into the controller BIOS. For further support contact the hardware vendor.
IV. Review the System Event Logs for hardware errors.
While in the Computer Management or the Server Management console, review the System Event Logs and see if there are any hardware errors being reported from the tape drive, robotic library, or controller cards. This is recommended even if the tape hardware is detected by Backup Exec/Windows and appears to be functioning properly.
The following are examples of hardware errors that might be present in the System Event Logs:
- Event ID 5: Signifies SCSI parity errors. This can be caused by a faulty SCSI card or faulty SCSI termination. If these errors occur, contact the hardware manufacturer.
- Event ID 7: Signifies bad blocks. This could be the result of a outdated tape device driver issue, faulty media, or dirty read/write heads on the tape drive. Update to the latest Backup Exec Tape Device Drivers, run a cleaning job and replace the media with new media if possible. If the issue continues with new media, please contact the hardware vendor.
- Event ID 9: Signifies SCSI bus timeouts. These errors usually occur when the SCSI bus resets itself, or the SCSI hardware does not respond in a timely fashion. Sometimes slowing the SCSI bus down can resolve these issues, as well as installing the latest SCSI drivers and firmware. Another device on the same cable can cause the issue too. In certain high end servers, moving the SCSI card to a different Peripheral Component Interconnect (PCI) slot, one that does not share the same bus as a RAID controller, has been known to fix these errors. If these errors occur, contact the hardware manufacturer.
- Event ID 11: Signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. Attempting to slow the SCSI bus down and verifying that the latest SCSI drivers and firmware are loaded can sometimes resolve these issues. If these errors occur, contact the hardware manufacturer.
- Event ID 15: Signifies the device is not ready for access. These errors usually occur when the device is malfunctioning or configured incorrectly. They may also occur if the incorrect drivers are loaded, or the drivers are not up to date. If these errors occur, contact the hardware manufacturer.
Advanced Troubleshooting Procedures:
V. Verify the device configuration is supported by Backup Exec
a. Verify that the inquiry
string matches the Hardware Compatibility List (HCL)
If the device is presenting
itself properly to the operating system, then it should be supplying the
operating system with an inquiry string.
In order for the device to work
properly within Backup Exec, the inquiry string the device provides must match
exactly with what is documented on the
HCL: http://entsupport.symantec.com/carveout_PID_15047_view_CL.htm
The inquiry string can be found
in two different places:
1. The ADAMM.LOG
file:
The adamm.log file is located in
x:\Program Files\Symantec\Backup Exec\. Open this log file using a text editor
such as Notepad, and scroll to the end of the log file. The adamm.log file
is appended to each time the Backup Exec services are started, and the detailed
information for each device is outputted to this log during a process called
Device Discovery.
Below is example output from a
Device Discovery (Figure 3):
Figure 3:
The above shows a single tape
drive (Tape0) and a robotic library (MediumChanger0). The Inquiry
String for the tape drive is QUANTUM SDLT320, and it is using firmware
version 2E2E. The robotic library has an inquiry string of QUANTUM
UHDL and is using firmware version 0016.
2. The DEVICEMAP
registry:
The Inquiry String, as well as
most of the Device Discovery information, can also be found in the DEVICEMAP
portion of the SCSI Registry:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi
Port #\Scsi Bus #\Target Id #\Logical Unit Id #\
The SCSI Port, SCSI Bus, SCSI ID
(TAR), and LUN Number can be found under the SCSI Address in Device Discovery in
the adamm.log file (highlighted in Figure3).
Below is the DEVICEMAP
registry hive from the tape drive from the above example (Figure
4):
Figure 4:
NOTE: The registry
settings under DEVICEMAP should not be edited, under any circumstances.
These keys should be automatically populated if the hardware is configured and
functioning properly.
Comparing the Inquiry Strings
with the HCL:
Locate the drive and/or library
on the HCL. Compare the Inquiry String found in the Step 1 or Step 2 to that
what is in the HCL. The inquiry string must match exactly between the HCL and
what is being reported to the server by the device.
NOTE: The ^ character in
the Inquiry Strings on the HCL represents the number of spaces that are expected
in the actual Inquiry String.
The following is from the HCL
for the above device (Figure 5):
Figure 5:
NOTE: The above (Figure
5) represents a single entry on the HCL, and would be found in a single line and
not on two entries.
b.Verify the connection
method matches the HCL.
In addition to verifying the
inquiry string, also verify that the method which the hardware is connected to
the server matches what is on the HCL (SCSI, Fibre, SAS, IDE, SATA). In
addition, tape drives should not be connected to RAID controllers.
Using the above example (Figure
5), this device is supported when connected via SCSI.
NOTE: There are many
devices that support multiple connection methods. In such examples, the device
would be listed twice on the HCL. If the device supports a connection method
that is not listed on the HCL, then it is possible that the device has not been
tested for such a connection and therefore support will be given a limited
basis. It is also possible that Symantec is in the process of qualifying the
particular device for that connection method. In these cases, please open a
support case with Symantec.
VI. Use tracer.exe to perform a SCSI trace while
restarting the Backup Exec services.
a. Stop the Backup Exec services and launch tracer.exe from the x:\Program Files\Symantec\Backup Exec\ directory. With tracer capturing SCSI information, restart the Backup Exec services using x:\Program Files\Symantec\Backup Exec\Servicesmgr.exe. Once the services have been restarted, review the tracer log for any hardware errors or reservation conflicts.
Please see the following document for more information on capturing and reading tracer logs:
Troubleshooting hardware with the Backup Exec for Windows Servers using the SCSI Trace Utility (tracer.exe).
http://support.veritas.com/docs/285630
a. Stop the Backup Exec services and launch tracer.exe from the x:\Program Files\Symantec\Backup Exec\ directory. With tracer capturing SCSI information, restart the Backup Exec services using x:\Program Files\Symantec\Backup Exec\Servicesmgr.exe. Once the services have been restarted, review the tracer log for any hardware errors or reservation conflicts.
Please see the following document for more information on capturing and reading tracer logs:
Troubleshooting hardware with the Backup Exec for Windows Servers using the SCSI Trace Utility (tracer.exe).
http://support.veritas.com/docs/285630
If the option is not selected,
select the option and proceed with the installation.
b. Verify that the SCSIChanger service is started.
If the library is not detected,
and robotic library support is enabled, verify that the SCSIChanger
service has been started. Click on Start > Run and type
msinfo32 and hit enter. Expand out Software Environment and the
click on System Drivers. Scroll down and find the SCSIChanger
service and verify that it is started (Figure 6):
Figure 6:
If the SCSIChanger service is
not started, or listed, then uninstall the Enable Robotic Library support option
and then reinstall it.
VII. Orphaned Devices in Windows Device Manager and/or devices no longer detected or offline in Backup Exec
Please see the following document for how to check for orphaned devices in Windows Device Manager:
How to remove old tape drivers from Windows that are no longer needed or in use.
http://support.veritas.com/docs/308914
It is quite possible that an orphaned devices may be present in Device Manager, especially after replacing hardware, or performing a firmware or driver update. Verify that there are no orphaned tape drives, medium changers, or controllers.
Remove any orphaned device(s) to eliminate any potential conflict.
VIII. Disable, delete and re-enable the device in Backup Exec
From the devices tab in Backup Exec, right-click the device and select Enable. This should remove the check mark next to the device and disable it. After disabling the device, right-click the device again, this time choosing delete.
NOTE: During the
delete process you may be prompted to re-target your backup jobs to other
devices or device pools. Please be mindful of the jobs to be re-targeted and
remember to change the jobs back after resolving the hardware issue.
After deleting the device(s), stop the Backup Exec services. With the services stopped, run Tapeinst.exe from x:\Program Files\Symantec\Backup Exec\. Choose the following options (Figure 8):
Figure 8:
Tracer.exe should also be running at this time as indicated in step #4 to review for any SCSI errors. Restart the Backup Exec services, and see if the devices are detected properly.
IX. Verify that the Device and Media Service is running under a Domain Admin account and/or built-in Administrator Account
If the media server is part of a domain, the Backup Exec Device and Media Service, in addition to all the Backup Exec Services (except the Remote Agent Service) should be using an account with Domain Admin privileges and/or built in Administrator Rights. Please see the Backup Exec Administrator's Guide for further information regarding the required rights for the Backup Exec services account.
For additional troubleshooting information, please refer to the TechNotes in the Related Documents Section below.
This document
is also available in the following languages:
French:
http://service1.symantec.com/SUPPORT/INTER/intl-on-technology.nsf/fr_docid/20080604143802975
German:
http://service1.symantec.com/SUPPORT/INTER/intl-on-technology.nsf/de_docid/20080604143854975
Italian:
http://service1.symantec.com/SUPPORT/INTER/intl-on-technology.nsf/it_docid/20080604143921975
German:
http://service1.symantec.com/SUPPORT/INTER/intl-on-technology.nsf/de_docid/20080604143854975
Italian:
http://service1.symantec.com/SUPPORT/INTER/intl-on-technology.nsf/it_docid/20080604143921975
http://support.veritas.com/docs/322812
http://support.veritas.com/docs/190653
http://support.veritas.com/docs/191158
http://support.veritas.com/docs/191694
http://support.veritas.com/docs/231488
http://support.veritas.com/docs/237047
http://support.veritas.com/docs/241684
http://support.veritas.com/docs/241706
http://support.veritas.com/docs/251466
http://support.veritas.com/docs/252385
http://support.veritas.com/docs/255502
http://support.veritas.com/docs/268942
http://support.veritas.com/docs/269214
http://support.veritas.com/docs/269712
http://support.veritas.com/docs/269843
http://support.veritas.com/docs/270077
http://support.veritas.com/docs/275454
http://support.veritas.com/docs/276143
http://support.veritas.com/docs/277425
http://support.veritas.com/docs/278111
http://support.veritas.com/docs/280026
http://support.veritas.com/docs/280508
http://support.veritas.com/docs/281310
http://support.veritas.com/docs/285630
http://support.veritas.com/docs/285732
http://support.veritas.com/docs/286598
http://support.veritas.com/docs/289555
http://support.veritas.com/docs/294326
http://support.veritas.com/docs/294545
http://support.veritas.com/docs/295508
http://support.veritas.com/docs/300454
http://support.veritas.com/docs/302699
http://support.veritas.com/docs/303436
http://support.veritas.com/docs/303504
http://support.veritas.com/docs/307422
http://support.veritas.com/docs/308027
http://support.veritas.com/docs/308914
http://support.veritas.com/docs/319285
http://support.veritas.com/docs/295757
http://support.veritas.com/docs/315349
http://support.veritas.com/docs/323433
http://support.veritas.com/docs/323456
http://support.veritas.com/docs/318581
http://support.veritas.com/docs/323364
http://support.veritas.com/docs/199542
http://support.veritas.com/docs/320867
http://support.veritas.com/docs/304178
http://support.veritas.com/docs/316894
http://support.veritas.com/docs/235210
http://support.veritas.com/docs/322814
http://support.veritas.com/docs/316878
http://support.veritas.com/docs/326507
http://support.veritas.com/docs/311736
http://support.veritas.com/docs/327704
Supplemental Material:
System: Ref.# | Description |
Error Code: e00084ed | A hardware error occurred |
UMI: V-79-57344-34029 | A hardware error occurred. |
Error Code: 0000045d | The request could not be performed because of an I/O device error. |
Error Code: 0xe000810b | Physical Volume Library Drive not found. |
UMI: V-79-57344-33035 | Physical Volume Library Drive not found. |
Error Code: 0xe00084ed | A hardware error occurred |
UMI: V-79-57344-34032 | The Device Timed Out |
Event ID: 5 | Parity errors |
Event ID: 7 | Bad blocks |
Event ID: 9 | SCSI bus timeouts |
Event ID: 11 | Controller errors |
Event ID: 15 | Device not ready |
UMI: V-79-57344-57350 | The Storage device reported a CRC error on a request to read/write data to/from media. This could be caused by either a dirty tape drive, bad media, or a SCSI problem. |
Error Code: 0xa00084f0 | The device timed out |
UMI: V-79-65535-34032 | The device timed out |
UMI: V-79-57344-34037 | Error e00084f5: The block sized being used is bad. |
Error Code: e00084f5 | The block sized being used is bad. |
UMI: V-79-57344-34001 | End of data was encountered before a set map could be located. |
Error Code: e00084d1 | End of data was encountered before a set map could be located. |
UMI: V-79-57344-33313 | Library error - the magazine is missing or not properly installed. |
Error Code: 0xE0008221 | Library error - the magazine is missing or not properly installed. |
UMI: V-79-57344-33317 | Library error - storage device is missing. |
Error Code: 0xE0008225 | Library error - storage device is missing. |
Fuente: http://support.veritas.com/docs/255501
Jorge.
Este comentario ha sido eliminado por un administrador del blog.
ResponderEliminarhеу therе and thank yοu for yοur info –
ResponderEliminarI've certainly picked up anything new from right here. I did however expertise some technical points using this site, as I experienced to reload the site a lot of times previous to I could get it to load properly. I had been wondering if your hosting is OK? Not that I am complaining, but sluggish loading instances times will sometimes affect your placement in google and can damage your high-quality score if advertising and marketing with Adwords. Anyway I'm adԁing this RЅS to my email
anԁ cоuld looκ out foг much more of your reѕpectіve exciting
сontent. Make ѕure you update thіs аgаin verу sοon.
Ηere iѕ mу websitе payday loans
Sorry to break your illusion, but Cutler himself has admitted that he uses steroids.
ResponderEliminarIf you google Ronnie Coleman steroids you'll get to a page where there's
a video in which Cutler admits himself and a lot of other pro
bodybuilders utilizing. He claims that they require to acquire an edge irrespective of what it
takes, after which he talks about steroids. So there you go.
Take a look at my web site :: six pack shortcuts members login page
hello there and thank you for your info – I've definitely picked up anything new from right here. I did however expertise several technical points using this website, as I experienced to reload the web site lots of times previous to I could get it to load properly. I had been wondering if your hosting is OK? Not that I am complaining, but sluggish loading instances times will sometimes affect your placement in google and can damage your quality score if advertising and marketing with Adwords. Anyway I am adding this RSS to my e-mail and could look out for a lot more of your respective intriguing content. Ensure that you update this again very soon.
ResponderEliminarMy blog post: visit us
Quаlіty poѕts іs the sеcret to be а focus for the useгs
ResponderEliminarto gο to see the ωeb page, that's what this site is providing.
Also visit my web-site reputation management
Some websites are there like females seeking men and men in search of girls in chennai/bangalore etc.
ResponderEliminar..But for that previous five many years am preserve on publishing and anticipating some reply from the lady.
But not but received any girl response..Could it be very good approach
to lookup girl buddy or searching woman buddy by means of internet site
by no means function out?.....then inform me another idear to get lady pal?
.......
Feel free to surf to my web blog - how to get a girls attention
Great job on these new articles or blog posts!
ResponderEliminarI
used to be constantly surprised how Bale was able to rework himself in
that short amount of your time.
Muscle Memory is
correct but I bet roids have been also concerned when you
said: his paycheck trusted it.
Also visit my homepage: building muscle mass diet for women
I loved as much as you'll receive carried out right here. The sketch is attractive, your authored subject matter stylish. nonetheless, you command get bought an impatience over that you wish be delivering the following. unwell unquestionably come further formerly again since exactly the same nearly a lot often inside case you shield this hike.
ResponderEliminarmy webpage; office furniture Services memphis tn
Good, I like which you share this online video Schooling is not the filling of a vessel,?
ResponderEliminarhowever the kindling of a flame, I want success always
Feel free to surf to my web site - tips to attract women on facebook
ResponderEliminarI am really impressed along with your writing skills and also with the format on your blog.
123.hp.com/setup 4500
ResponderEliminarAwesome blog! I am really impressed by this blog! The pictures are really nice and cool
123 HP Setup
Thanks for sharing information.
ResponderEliminarRobots and Device Solutions
Wow this blog is very nice …Crafsol is India's best Robots and Device Solutions Company
ResponderEliminarRobots and Device Solutions
Thank you for the insights offered in the article. Looking for more such pieces. Visit our sites for printer setup & support.
ResponderEliminar123.hp.com || 123.hp.com/setup || 123HP Setup || hp.com/setup || hp.com/123 || 123.hp.com setup || 123 HP Printer Setup || 123 HP Printer Support || 123 HP Setup and Install || 123hpcom || 123 HP Printer Install || 123hpcomsetup || 123 HP Wireless Setup || 123 HP Install || hpcom/123 || 123hpcominstall || 123HP Setup || 123 HP Smart App || Install 123 HP Printer || HP 123 Setup Scanner
Wow...! awesome you did a great job and superb blog thank you so much for this blog. Here I want to tell something about the configure Gmail configuration in Microsoft outlook those who all want to know about the email configuration in outlook please refer my site.
ResponderEliminarThank you so much for this fantastic blog, The windows update error 80072ee2 message is displayed on the screen when the update process fails or files stored on your system are corrupted. To fix the error 80072ee2 on windows 10, read the troubleshooting instructions that are listed here.
ResponderEliminarThank you so much for this blog, If you are not receiving emails on your POP3(Post Office Protocol version 3) account in Outlook 2016, check the internet connection first and restart your Outlook application. Close all other running applications running on your computer. Check if you are using the obsolete OS version.
ResponderEliminarThanks a lot for this awesome one..! The brother mfc j6945dw scan to email function can be done following the procedure press the settings icon on the control pannel's LCD screen navigate to all settings and select print reports choose network configuration from this list, this is the basic functions if want to know more about this visit this site.
ResponderEliminarThanks a lot for this blog..! Windows update error code 8007000e on your computer this is simple to fix an easy way of methods, some of the methods are listed below if you want to know about this error code visit here also solve the related error codes.
ResponderEliminarThank you so much...Post Office Protocol version 3 is the updated version of POP. The POP3 is a server protocol that is responsible for downloading or receiving e-mails from the internet server and also do configure Gmail in outlook 2007. If you have more doubts please visit us.
ResponderEliminarAwesome blog thank you so so much..,The Brother MFC J6945DW scan to e-mail function can be done following the procedure given below. Brother printer has done the multi-task when compared to your older printer, it has the new features so visit here and know what are the features available.
ResponderEliminarThank you so much for this blog, certain PS's enabled on windows 10 come with SIM cards that allow you to connect to a mobile network and configure cellular settings in windows 10. This means that you can get over a network wherever you have a cellular signal.
ResponderEliminarThank you so much for this giving blog, Here I want to say about the brother MFC j6945dw printer wired setup. if you want to know about this printer please refer to my site.
ResponderEliminar