{"id":30016,"date":"2017-04-04T08:30:25","date_gmt":"2017-04-04T15:30:25","guid":{"rendered":"https:\/\/virtual-dba.com\/?p=30016"},"modified":"2021-02-10T18:11:18","modified_gmt":"2021-02-11T01:11:18","slug":"changing-storage-in-an-always-on-environment","status":"publish","type":"post","link":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/","title":{"rendered":"Changing Storage in an Always On Environment"},"content":{"rendered":"

I was recently given a task to move a few multi-terabyte databases inside of an availability group from SAN A to SAN B within a 10-minute window. The good news was there was plenty of time to plan and prepare. For the purpose of this example, I will be using a very small database and just moving from the C: drive to a D: drive; but functionally and, in principle, it is the same. As you can see below the files for the database 12AG are located on the C: drive.<\/span><\/p>\n

We will accomplish the move using log shipping. This approach allows us to stage the entire database on the new storage and keep it updated until we reach our maintenance window.  While I am not going to go into detail on how to setup log shipping, I will say it needs to be configured on the primary replica. In this example, I configured log shipping to ship from the primary replica to the primary replica to a database with a different name. See below:<\/span><\/p>\n

\"database-12AG-c-drive\"<\/span><\/p>\n

Steps to Take<\/span><\/h2>\n

Once you have log shipping setup and the log shipped database is current, you are ready to begin your maintenance window. The following steps will allow you to change storage and keep you AG in sync with minimal downtime.<\/span><\/p>\n

1. Disable the log shipping backup jobs.<\/span><\/p>\n

We do this to ensure we know exactly where we are in the backup chain. Further, we will take two final log backups which will need to be manually restored, and it will be much easier if we don\u2019t have to worry about additional log files from the log shipping routines.<\/span><\/p>\n

2. Manually run the copy and restore job to ensure all of the logs are processed to the temporary LS database (DBName -12AG).<\/span><\/span><\/p>\n

Run the copy and restore jobs to ensure that we have completed the log shipping aspect of the move. We will clean up the log shipping artifacts later, as we don\u2019t want to take steps that can be done outside of the window until we have completed the move.<\/span><\/p>\n

3. Connect to the primary replica, verify that all of the secondary nodes are synchronized and remove the database from the availability group.<\/span><\/span><\/p>\n

\"remove-database-availability-group\"<\/p>\n

This step will cause all of the secondary nodes to revert back to a restoring state\u2014and become unreadable. If you have routing configured, it will no longer send read-only requests to the secondary replicas. At this time, your application will not longer be able to connect.<\/span><\/p>\n

4. Create a manual transaction log backup of the source database – (DBName – 12AG on the primary Replica)<\/span><\/span><\/p>\n

a. Select the Backup the tai<\/strong>l of the log and leave the database in the restoring state<\/b> to ensure no additional transactions are allowed<\/span><\/p>\n

b. Be sure to note the location and name of this out of band log backup as it will need to manually restored to the temp LS database (DBName – 12AG) as well as the database on all replicas in the AG<\/span><\/p>\n

This step sets the database on the primary replica to a restoring state. This is important because not everyone has the ability to fully stop their application. By doing this, it will ensure that all transactions are captured and prevent any additional transactions from being written.  <\/span><\/p>\n

Depending on your environment and how busy your database is, you may run into an issue where exclusive access cannot be attained, and are therefore unable to perform this action. Because of this possibility, I recommend scripting the log backup with the tail of the log. This will enable you to script putting the database into single user mode and executing the log backup from the same window. The script can be generated from the clicking script on the backup window, but do not set to single user and then try to do the backup via the GUI. You risk the connection being grabbed by another process\u2014and then you\u2019ll be scrambling.<\/span><\/p>\n

USE<\/span> master<\/span><\/span>;<\/span>
\n<\/span> GO<\/span>
\n<\/span> ALTER<\/span> DATABASE<\/span><\/span> 12AG<\/span>
\n<\/span> SET<\/span> SINGLE_USER<\/span>
\n<\/span> WITH<\/span> ROLLBACK<\/span> IMMEDIATE<\/span><\/span>;<\/span><\/span><\/p>\n

*SQL Authority does a good job of explaining the ‘with rollback immediate’ option if you’re not familiar with it <\/span>here<\/span><\/a>.<\/span><\/span><\/p>\n

\"backup-database\"<\/p>\n

5. Restore the transaction log you just took (of DBName – 12AG) to the primary Replica\u2019s log shipped database (DBName -12AGTemp) using the \u2018with recovery\u2019 option.<\/span><\/p>\n

6. Delete the original database on the primary replica (DBName – 12AG)<\/span><\/span><\/p>\n

DROP DATABASE 12AG<\/span><\/span><\/p>\n

While this step sounds scary, it is necessary. When you set up the log shipped database, you\u2019re required to give it a different name than the original database. After you drop the original database, we will rename this database the original name.<\/span><\/p>\n

7. Set the log shipped database to Multi-User<\/span><\/p>\n

We set the database to Multi-User before renaming because, once the database is renamed, read\/write connections will be accepted from the application on the primary replica. If we rename prior to setting to multi-user, we risk losing the connection since the database was set to single user.<\/span><\/span><\/p>\n

USE<\/span> master<\/span><\/span>;<\/span>
\n<\/span> GO<\/span>
\n<\/span> ALTER<\/span> DATABASE<\/span><\/span> 12AGtemp<\/span>
\n<\/span> SET<\/span> MULTI_USER<\/span>
\n<\/span> WITH<\/span> ROLLBACK<\/span> IMMEDIATE<\/span><\/span>;<\/span><\/span><\/span><\/p>\n

8. Rename the log shipped database to the original database name.<\/span><\/p>\n

USE<\/span> master<\/span><\/span>;<\/span>
\n<\/span> GO<\/span>
\n<\/span> ALTER<\/span> DATABASE<\/span><\/span> 12AGtemp<\/span>
\n<\/span> Modify Name<\/span> = <\/span>[12AG];<\/span><\/span><\/span><\/p>\n

9. Take a 2nd transaction log backup of the newly renamed database on the primary replica<\/span><\/p>\n

We have to take a 2nd transaction log backup because the first transaction log backup has the read-only flag set. This will keep us from being able to add the database back to the availability group on the secondary replicas.<\/span><\/span><\/p>\n

10. Restore both of the transaction logs to all secondary replicas using the No Recovery<\/strong> option<\/span><\/p>\n

If you recover the database on the secondary replicas, you will have to reinitialize the database on that replica. Since we are trying to do this with as little downtime as possible given our requirements, the importance of using the no recovery option on the secondary replicas is significant.<\/span><\/p>\n

11. On the primary replica, join the database back to the availability group using the Join Only<\/strong> option.<\/span><\/p>\n

12.\"add-database\"<\/span><\/p>\n

\"add-database-availability-group\"<\/p>\n

13. Verify synchronization and connectivity.<\/span><\/p>\n

You can see from the dashboard all of our replicas are functioning as expected and available for either read\/write or read connections, as defined in the availability group. The 3rd node is an asynchronous replica. Its state is synchronizing and could allow for data loss in the event of a manual failover, but still accepts new transactions.<\/span><\/p>\n

\"replica-dashboard\"<\/p>\n

We can also verify our files are now in the new location.<\/span><\/p>\n

\"files-in-new-location\"<\/p>\n

At this point, your application should be fully up and running. Read-only requests will route to the appropriate replica (if you have that configured) and you can end your maintenance window.<\/span><\/p>\n

14. Clean up log shipping artifacts<\/span><\/p>\n

Since log shipping is based on database name, the database will still be configured for log shipping. All we need to do is disable the database for log shipping, and SQL Server will clean up all of the artifacts\u2014including the jobs.<\/span><\/p>\n

\"enable-as-primary-database-in-log-shipping-configuration\"<\/p>\n

As you can see, we are able to move locations with minimal downtime by using this approach.  We could further reduce the downtime by scripting the log backups and restores in advance on all replicas, as well as the adding the database back into the availability group. By scripting each step, you will be able to move the storage as fast as a log backup and restore will take (with only a few additional seconds) to remove and join the database to the availability group. As with any process, you should test this and be very comfortable with each step prior to running in a production environment.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

I was recently given a task to move a few multi-terabyte databases inside of an availability group from SAN A to SAN B within a 10-minute window. The good news was there was plenty of time to plan and prepare. For the purpose of this example, I will be using a very small database and […]<\/p>\n","protected":false},"author":3,"featured_media":30256,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[4166,55],"tags":[1957,1843,1842,60],"class_list":["post-30016","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-sql-server","tag-always-on","tag-availability-group","tag-log-shipping","tag-sql-server"],"yoast_head":"\nChanging Storage in an Always On Environment in SQL Server<\/title>\n<meta name=\"description\" content=\"Moving large databases inside an availability group using the "log shipping" method. Learn how this can be done in SQL Server.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Changing Storage in an Always On Environment\" \/>\n<meta property=\"og:description\" content=\"Moving large databases inside an availability group using the "log shipping" method. Learn how this can be done in SQL Server.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/\" \/>\n<meta property=\"og:site_name\" content=\"Virtual-DBA Remote DBA Services & Support - Certified Database Experts\" \/>\n<meta property=\"article:published_time\" content=\"2017-04-04T15:30:25+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-02-11T01:11:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/virtual-dba.com\/media\/changing-storage-always-on-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"546\" \/>\n\t<meta property=\"og:image:height\" content=\"287\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"XTIVIA\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@virtual_dba\" \/>\n<meta name=\"twitter:site\" content=\"@virtual_dba\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"XTIVIA\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/\"},\"author\":{\"name\":\"XTIVIA\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1\"},\"headline\":\"Changing Storage in an Always On Environment\",\"datePublished\":\"2017-04-04T15:30:25+00:00\",\"dateModified\":\"2021-02-11T01:11:18+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/\"},\"wordCount\":1275,\"commentCount\":3,\"publisher\":{\"@id\":\"https:\/\/virtual-dba.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg\",\"keywords\":[\"always on\",\"availability group\",\"log shipping\",\"sql server\"],\"articleSection\":[\"Blog\",\"SQL Server\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/\",\"url\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/\",\"name\":\"Changing Storage in an Always On Environment in SQL Server\",\"isPartOf\":{\"@id\":\"https:\/\/virtual-dba.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg\",\"datePublished\":\"2017-04-04T15:30:25+00:00\",\"dateModified\":\"2021-02-11T01:11:18+00:00\",\"description\":\"Moving large databases inside an availability group using the \\\"log shipping\\\" method. Learn how this can be done in SQL Server.\",\"breadcrumb\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage\",\"url\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg\",\"contentUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg\",\"width\":546,\"height\":287,\"caption\":\"changing-storage-always-on-environment\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/virtual-dba.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Changing Storage in an Always On Environment\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/virtual-dba.com\/#website\",\"url\":\"https:\/\/virtual-dba.com\/\",\"name\":\"Virtual-DBA Remote DBA Services & Support - Certified Database Experts\",\"description\":\"Remote Database Administration\",\"publisher\":{\"@id\":\"https:\/\/virtual-dba.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/virtual-dba.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/virtual-dba.com\/#organization\",\"name\":\"Virtual-DBA: Remote DBA | Remote Database Administration\",\"alternateName\":\"Virtual-DBA powered by XTIVIA\",\"url\":\"https:\/\/virtual-dba.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg\",\"contentUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg\",\"width\":557,\"height\":291,\"caption\":\"Virtual-DBA: Remote DBA | Remote Database Administration\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/virtual_dba\",\"https:\/\/www.linkedin.com\/showcase\/36220649\/\",\"https:\/\/www.youtube.com\/channel\/UCx3AIeUQ2ziTLKZSJDZ-SEg\"],\"description\":\"Eliminate database downtime and spiraling costs with XTIVIA\u2019s Virtual-DBA. In today\u2019s always-on business world, gaps in 24x7 on-call DBA support, neglected maintenance and security, or a stretched team struggling with overwhelming workloads can lead to costly disruptions and threaten business continuity. XTIVIA\u2019s Virtual-DBA provides the immediate, expert database administration you need, exactly when you need it, ensuring optimal performance, ironclad security, and significant cost savings without the burden of expanding your in-house team. The goal of Virtual-DBA is to provide a cost-effective solution for organizations seeking to optimize the security, management, maintenance, availability, and performance of their critical business systems, whether self-managed or cloud-managed (e.g., AWS RDS, Azure SQL Database). We accomplish this through a comprehensive remote DBA service offering designed specifically to meet the Oracle\u00ae, DB2\u00ae, Informix\u00ae, MySQL\u2122, PostgreSQL\u00ae, MongoDB\u00ae, MariaDB, and Microsoft SQL Server\u00ae, CockroachDB, Databricks, AWS, and Azure needs of our clients.\",\"email\":\"info@xtivia.com\",\"telephone\":\"8886853101\",\"legalName\":\"XTIVIA, Inc\",\"foundingDate\":\"1992-05-01\",\"numberOfEmployees\":{\"@type\":\"QuantitativeValue\",\"minValue\":\"201\",\"maxValue\":\"500\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1\",\"name\":\"XTIVIA\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g\",\"caption\":\"XTIVIA\"},\"url\":\"https:\/\/virtual-dba.com\/author\/xtivia\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Changing Storage in an Always On Environment in SQL Server","description":"Moving large databases inside an availability group using the \"log shipping\" method. Learn how this can be done in SQL Server.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/","og_locale":"en_US","og_type":"article","og_title":"Changing Storage in an Always On Environment","og_description":"Moving large databases inside an availability group using the \"log shipping\" method. Learn how this can be done in SQL Server.","og_url":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/","og_site_name":"Virtual-DBA Remote DBA Services & Support - Certified Database Experts","article_published_time":"2017-04-04T15:30:25+00:00","article_modified_time":"2021-02-11T01:11:18+00:00","og_image":[{"width":546,"height":287,"url":"https:\/\/virtual-dba.com\/media\/changing-storage-always-on-1.jpg","type":"image\/jpeg"}],"author":"XTIVIA","twitter_card":"summary_large_image","twitter_creator":"@virtual_dba","twitter_site":"@virtual_dba","twitter_misc":{"Written by":"XTIVIA","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#article","isPartOf":{"@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/"},"author":{"name":"XTIVIA","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1"},"headline":"Changing Storage in an Always On Environment","datePublished":"2017-04-04T15:30:25+00:00","dateModified":"2021-02-11T01:11:18+00:00","mainEntityOfPage":{"@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/"},"wordCount":1275,"commentCount":3,"publisher":{"@id":"https:\/\/virtual-dba.com\/#organization"},"image":{"@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage"},"thumbnailUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg","keywords":["always on","availability group","log shipping","sql server"],"articleSection":["Blog","SQL Server"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/","url":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/","name":"Changing Storage in an Always On Environment in SQL Server","isPartOf":{"@id":"https:\/\/virtual-dba.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage"},"image":{"@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage"},"thumbnailUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg","datePublished":"2017-04-04T15:30:25+00:00","dateModified":"2021-02-11T01:11:18+00:00","description":"Moving large databases inside an availability group using the \"log shipping\" method. Learn how this can be done in SQL Server.","breadcrumb":{"@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#primaryimage","url":"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg","contentUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/changing-storage-always-on-1.jpg","width":546,"height":287,"caption":"changing-storage-always-on-environment"},{"@type":"BreadcrumbList","@id":"https:\/\/virtual-dba.com\/blog\/changing-storage-in-an-always-on-environment\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/virtual-dba.com\/"},{"@type":"ListItem","position":2,"name":"Changing Storage in an Always On Environment"}]},{"@type":"WebSite","@id":"https:\/\/virtual-dba.com\/#website","url":"https:\/\/virtual-dba.com\/","name":"Virtual-DBA Remote DBA Services & Support - Certified Database Experts","description":"Remote Database Administration","publisher":{"@id":"https:\/\/virtual-dba.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/virtual-dba.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/virtual-dba.com\/#organization","name":"Virtual-DBA: Remote DBA | Remote Database Administration","alternateName":"Virtual-DBA powered by XTIVIA","url":"https:\/\/virtual-dba.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/","url":"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg","contentUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg","width":557,"height":291,"caption":"Virtual-DBA: Remote DBA | Remote Database Administration"},"image":{"@id":"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/virtual_dba","https:\/\/www.linkedin.com\/showcase\/36220649\/","https:\/\/www.youtube.com\/channel\/UCx3AIeUQ2ziTLKZSJDZ-SEg"],"description":"Eliminate database downtime and spiraling costs with XTIVIA\u2019s Virtual-DBA. In today\u2019s always-on business world, gaps in 24x7 on-call DBA support, neglected maintenance and security, or a stretched team struggling with overwhelming workloads can lead to costly disruptions and threaten business continuity. XTIVIA\u2019s Virtual-DBA provides the immediate, expert database administration you need, exactly when you need it, ensuring optimal performance, ironclad security, and significant cost savings without the burden of expanding your in-house team. The goal of Virtual-DBA is to provide a cost-effective solution for organizations seeking to optimize the security, management, maintenance, availability, and performance of their critical business systems, whether self-managed or cloud-managed (e.g., AWS RDS, Azure SQL Database). We accomplish this through a comprehensive remote DBA service offering designed specifically to meet the Oracle\u00ae, DB2\u00ae, Informix\u00ae, MySQL\u2122, PostgreSQL\u00ae, MongoDB\u00ae, MariaDB, and Microsoft SQL Server\u00ae, CockroachDB, Databricks, AWS, and Azure needs of our clients.","email":"info@xtivia.com","telephone":"8886853101","legalName":"XTIVIA, Inc","foundingDate":"1992-05-01","numberOfEmployees":{"@type":"QuantitativeValue","minValue":"201","maxValue":"500"}},{"@type":"Person","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1","name":"XTIVIA","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g","caption":"XTIVIA"},"url":"https:\/\/virtual-dba.com\/author\/xtivia\/"}]}},"_links":{"self":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts\/30016","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/comments?post=30016"}],"version-history":[{"count":0,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts\/30016\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/media\/30256"}],"wp:attachment":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/media?parent=30016"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/categories?post=30016"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/tags?post=30016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}