Two strange issues

  • Hi Everyone. 

    I have 2 strange issues that have just come up

    Before discussing the issues I just want to preface that I just changed the server where I store my backups - these issues did not appear before this  - the new path is

    \\server\sqlbackups\SVRname\ - then it creates it own directory

    the logs go to \\server\sqlbackups\SVRname\LOG

    Now the problem

    1 - In taskpad view in EM - the last backup date is wrong.  This is not life threating - but I have to say my heart skipped a beat when i saw that 9/13/2004 date for last backup!!!      The date is wrong for only 4 DB and they are all 3 Gb in size??  The smaller ones are fine 

    2 - I get a failed error on my backups too! As stated above, the BAK and TRN files are there BUT the report files are empty.  I will guess that that is why I get a fail message?  Why are they empt is there a limit to the # of directories yu can use to in storing backups and report  files

    Thank in advance - Karen

     

     

  • 1. Maybe taskpad / em is out of sync. Close EM and check again. The last backup date is the last successful backup, so if the backups are failing, then that date will still be old.

    2. Maybe there is a permission issue, or space limitation, or another reason why the backups are failing. IF you are using a Maintenance Plan to backup, right click the plan and go into History. Tick the check box to show step history and see what the exact error is.

    Maybe there is a limitation on the network server filesystem that limits to files 3GB in size?

     


    Julian Kuiters
    juliankuiters.id.au

  • Karen,

    If your new server is Windows 2003 this article might help you

    http://support.microsoft.com/default.aspx?scid=kb;en-us;827452.

    But it does not anything about 3GB file size limit.

    Igor

  • Enterprise Manager sometimes has trouble keeping up it's information. Sometimes running DBCC UPDATEUSAGE works. Might also run sp_updatestats.

    -SQLBill

  • Something else to check. Make sure the date/time on the target server is synchronized with the rest of the network.

    Since you are using UNC paths to put your backups on another server, make sure you have proper permission. The Backup job when run under the agent has different permissions than when you run the same thing from EM.

    We had a similar situation where the target server was using disk compression and that was causing the failure. We also had another where the target server was using MS Windows RAID/spanning and it would fail with backups over 1GB in size.

    Hope this helps!

    SJ

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply