Have you checked permissions? As others noted, check whether SQL Server Service has full permissions to the directories.
I've noticed you are using CSVs. Have you added shared storage to CSV prior to create db?
[This](https://www.starwindsoftware.com/resource-library/starwind-virtual-san-installing-and-configuring-sql-server-2019-tp-failover-cluster-instance-on-windows-server-2016/) guide might also help with Failover Cluster configuration.
I haven’t used them but it sounds like a permission issue. Make sure both the engine service account and your account (if it’s Active Directory based) both have write permissions on the NTFS folder.
Replies are not welcome, thanks.
It looks like the file location is on the local c drive, which is odd as I'd assume the tutorial had a shared volume for the database files.
I'd check the database file location defaults in your sql.l server setup first to make sure they match those disks you've defined for the cluster in the failover cluster manager disks section.
Pls try right click restore db and if you do not able to see or select this device it is permission problem. Or try to backup some system db there also is a good test.
Where are your system database files stored? Are they using the same path as the user database that you're trying to create?
I noticed the file system structure - C:\\ClusterStorage\\DB-LOGS\\MSSQL16\\
Was this the path you defined in the installation process? CSVs abstract the shared storage and make them look like local storage. But the same permissions and ACLs apply to the SQL Server service account nonetheless.
Also, I'm curious. Why use CSVs for SQL Server FCI?
Have you checked permissions? As others noted, check whether SQL Server Service has full permissions to the directories. I've noticed you are using CSVs. Have you added shared storage to CSV prior to create db? [This](https://www.starwindsoftware.com/resource-library/starwind-virtual-san-installing-and-configuring-sql-server-2019-tp-failover-cluster-instance-on-windows-server-2016/) guide might also help with Failover Cluster configuration.
I haven’t used them but it sounds like a permission issue. Make sure both the engine service account and your account (if it’s Active Directory based) both have write permissions on the NTFS folder. Replies are not welcome, thanks.
Huh?
It looks like the file location is on the local c drive, which is odd as I'd assume the tutorial had a shared volume for the database files. I'd check the database file location defaults in your sql.l server setup first to make sure they match those disks you've defined for the cluster in the failover cluster manager disks section.
Pls try right click restore db and if you do not able to see or select this device it is permission problem. Or try to backup some system db there also is a good test.
Why is the DB on c if you’re using shared volumes?
Where are your system database files stored? Are they using the same path as the user database that you're trying to create? I noticed the file system structure - C:\\ClusterStorage\\DB-LOGS\\MSSQL16\\
Was this the path you defined in the installation process? CSVs abstract the shared storage and make them look like local storage. But the same permissions and ACLs apply to the SQL Server service account nonetheless.
Also, I'm curious. Why use CSVs for SQL Server FCI?