none
Backup Time is extremly HIGH

    Question

  • Hi,

     We have  Windows 2003 Server Failover cluster server. One of the storage disk have some SAN patch issue - among 2, one SAN path is not working. Storage is HP EVA. Problem is that one of storage disk have around 1 TB space & one of file of the disk around 550 GB. Disk is almost 90% utilized. Usually backup with DP 6.2 through SAN multipath took 3 Hr. (before SAN patch issue). Now a days backup taking time between 8 to 12 hrs., it varies, but my total backup size is not varied - it remain between 850 GB to 900 GB. Also checked that specifically the large 550 GB file taking too much time for backup. I am suspecting the large file have some issue. How to check this file as well as the storage disk also. I am agree that for SAN path issue backup time is taking much time, considering this I need to check the file consistency & the respective disk. How to do this ? Reply please.

    S Mandal

    Friday, June 08, 2018 8:00 AM

Answers

  • Hi S Mandal,

    Please check if any other process is running and utilizing more CPU and memory.

    The time taken is dependent on a host of factors like network latency, available IOPS on the primary storage account, available IOPS on the backup storage account etc, so we would need to isolate exactly what is causing this delay.
    Have you checked the operation logs to see if it shows anything that might help us. A
    ny error/warning in the event viewer?

    In addition, since windows server 2003 is out of support. It is suggested you upgrade your server.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 08, 2018 9:09 AM
    Moderator
  • Hi Marry,

    Thank you for reply. After checking all the possibilities, I am sure the only SAN path is not only for backup, it is also occupied for other jobs - server is online & continuously access by other process. So ultimately one SAN path can provide a less bandwidth for backup.Hence it was taking more time. You are right.

    S Mandal

    • Marked as answer by Suddhaman Monday, August 06, 2018 4:16 PM
    Monday, August 06, 2018 4:16 PM

All replies

  • Hi S Mandal,

    Please check if any other process is running and utilizing more CPU and memory.

    The time taken is dependent on a host of factors like network latency, available IOPS on the primary storage account, available IOPS on the backup storage account etc, so we would need to isolate exactly what is causing this delay.
    Have you checked the operation logs to see if it shows anything that might help us. A
    ny error/warning in the event viewer?

    In addition, since windows server 2003 is out of support. It is suggested you upgrade your server.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 08, 2018 9:09 AM
    Moderator
  • Hi,
    Could the above reply be of help? If yes, you may mark it as answer, if not, feel free to feed back
    Best Regards,
    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 13, 2018 8:06 AM
    Moderator
  • Hi Marry,

    Thank you for reply. After checking all the possibilities, I am sure the only SAN path is not only for backup, it is also occupied for other jobs - server is online & continuously access by other process. So ultimately one SAN path can provide a less bandwidth for backup.Hence it was taking more time. You are right.

    S Mandal

    • Marked as answer by Suddhaman Monday, August 06, 2018 4:16 PM
    Monday, August 06, 2018 4:16 PM