SQL2036N when backing up to CIFS

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Victor Alvarez
    #1

    SQL2036N when backing up to CIFS

    Hi,

    I'm not sure if anyone can help with this issue I have, but I would
    appreciate any thoughts.

    We are running DB2 8.2, fp11 on windows 2003. The goal is to backup to
    an external EMC SAN which uses CIFS. Is this possible?

    It was my understanding that backups were file system independent. I
    have also successfully backed up onto an NTFS network drive, so the
    remote drive issue doesn't appear to be a problem for DB2 either.

    This leaves me with the possibility that the backup isn't doable
    because we are using different file systems (NTFS to CIFS), that there
    is a permissions issue on our particular SAN, or some other factor I
    haven' considered.

    Any ideas?

    Tags: None
    • Ian
      #2
      Re: SQL2036N when backing up to CIFS

      Victor Alvarez wrote:
      Hi,
      >
      I'm not sure if anyone can help with this issue I have, but I would
      appreciate any thoughts.
      >
      We are running DB2 8.2, fp11 on windows 2003. The goal is to backup to
      an external EMC SAN which uses CIFS. Is this possible?
      >
      It was my understanding that backups were file system independent. I
      have also successfully backed up onto an NTFS network drive, so the
      remote drive issue doesn't appear to be a problem for DB2 either.
      >
      This leaves me with the possibility that the backup isn't doable
      because we are using different file systems (NTFS to CIFS), that there
      is a permissions issue on our particular SAN, or some other factor I
      haven' considered.
      >
      Any ideas?
      >
      DB2 does support writing to shares (the type of file system is
      immaterial).

      However, there are some restrictions:

      1) You can't backup to a network drive (i.e. H:\, which is mapped
      to \\server\share) , because the share isn't visible to the DB2
      service. You have to use a UNC path, i.e.

      backup database X to \\server\share



      2) The account that the DB2 service Logs on As must have permission
      to access the share.

        Comment

        • Victor Alvarez
          #3
          Re: SQL2036N when backing up to CIFS

          Thanks Ian, this is what I imagined.

          I'll have to speak with the SAN admin.


          Ian wrote:
          Victor Alvarez wrote:
          Hi,

          I'm not sure if anyone can help with this issue I have, but I would
          appreciate any thoughts.

          We are running DB2 8.2, fp11 on windows 2003. The goal is to backup to
          an external EMC SAN which uses CIFS. Is this possible?

          It was my understanding that backups were file system independent. I
          have also successfully backed up onto an NTFS network drive, so the
          remote drive issue doesn't appear to be a problem for DB2 either.

          This leaves me with the possibility that the backup isn't doable
          because we are using different file systems (NTFS to CIFS), that there
          is a permissions issue on our particular SAN, or some other factor I
          haven' considered.

          Any ideas?
          >
          DB2 does support writing to shares (the type of file system is
          immaterial).
          >
          However, there are some restrictions:
          >
          1) You can't backup to a network drive (i.e. H:\, which is mapped
          to \\server\share) , because the share isn't visible to the DB2
          service. You have to use a UNC path, i.e.
          >
          backup database X to \\server\share
          >
          >
          >
          2) The account that the DB2 service Logs on As must have permission
          to access the share.

            Comment

            Previous template Next
            Working...