Share via

Question on backing up clustered instance

Mikhail Firsov 1,881 Reputation points
2021-09-17T09:23:17.703+00:00

Hello,

It's rather strange but I failed to find information about best practices on backing up clustered SQL Server instances in my MS textbooks (official curriculums) as well as on the technet - would anyone please share a link to such documents should they exist?

I'm asking that question because I can't seem to make my clustered SQL Server instance to backup to another shared drive (another LUN) which I've already added to the SQL Server's resource group - it can only "see" the LUN (disk) which had been selected during setup...

Thank you in advance,
Michael

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments No comments

Answer accepted by question author

Olaf Helper 47,616 Reputation points
2021-09-17T09:36:44.05+00:00

It doesn't matter if it's a cluster or stand-alone server, SQL Server backup works always the same way

backup to another shared drive

If you mean a NAS share, the you can not "see" it in backup wizard.
You have to use plain T-SQL backup command and address the share by UNC path.

Was this answer helpful?

0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Mikhail Firsov 1,881 Reputation points
    2021-09-17T13:31:27.533+00:00

    P.S. Here're the two jobs: the first is part of the maintenance plan (backup to e: as mentioned above - just the selected checkbox next to "Backup DB"), the second is the manually-created job -

    BACKUP DATABASE Resources  
     TO DISK = 'E:\JOBbackups\DB.bak'  
        WITH FORMAT;  
    GO  
    

    The results are as follows:
    133069-q3.png

    The most interesting fact: backups are getting created in both cases! In spite of the error in the first case the backup that's being created by the maintenance plan is totally correct (I've tested it by restoring the db from it) - no comments...

    Was this answer helpful?

    0 comments No comments

  2. Mikhail Firsov 1,881 Reputation points
    2021-09-17T10:42:16.84+00:00

    Ok, I understand - thank you for the explanation!

    I also tried to create a maintenance plan (backup db, log...) now and it was created using the default drive (LUN), but it allowed me to change the destination folder by typing in the path to the other LUN and the plan did produced the backups on that (E:) drive (there was strange errorduring the execution but all database and log backups have been created):
    133124-q1.png

    133048-q2.png

    ...can't understand 1) the behaviour of the backup wizard 2) why this is not documented (at least I've never seen it in documents/guides/textbooks)... :(

    Was this answer helpful?

    0 comments No comments

  3. Mikhail Firsov 1,881 Reputation points
    2021-09-17T09:59:03.817+00:00

    Yes, T-SQL Backup statement worked out perfect - but why does the SQL Server's backup wizard "see" just the drive (LUN) where its databases are located? Is it a bug or it's by design? I would never have guessed that the wizard can't see what the TSQL can see...

    By the way:
    "It doesn't matter if it's a cluster or stand-alone server, SQL Server backup works always the same way
    backup to another shared drive
    "

    1) the "stand-alone version of the wizard" always does see the same set of disks as TSQL sees
    2) what does mean "shared drive" in the context of the single server???

    Regards,
    Michael

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.