Hi everybody!
We want to implement the SQL intelligent policy on our SQL cluster (VCS). But faced the trouble.
We have two different datacenters. SQL cluster deployed on 4 physical servers (two in each DC) and backup traffic between DCs is undesirable.
How can we set up the policy(-ies) to use storage unit from DC where SQL cluster instance is active at the certain moment during backup?
If memory serves me right, we have solved this issue like this (using traditional script-base policies):
Create 2 (or more, depending on number of nodes and sites) Application Backup schedules in the policy (e.g. siteA and siteB). Override the STU in each of the schedules to select either siteA or siteB Storage Unit.
Copy the backup script to local storage on each of the nodes.
Add NBSCHED variable to each script that specifies the Application Backup schedule with local STU.
Hope this makes sense!
Create a Policy at each data center for local backup. Activate the Policy at the live site and Deactivate the Policy at the idle site. Don't know of any automated way to handle that.
Hello,
refer to "virtual storage units" topic in High Availability Guide (pages 22-27).
No matter if they are used with SQL intelligent policy or any other type of policies.
Regards
Michal
Many thanks to all for answers. I contacted to veritas support yesterday. They confirmed there no features at the moment for resolving this issue. And suggested to use scripts too.
As Michal suggested you can use the app_cluster feature in netbackup. Its usually used within a site but it would probably work across sites too. Failing that, you can put a preonline trigger into vcs to execute a policy storage location update prior to onlining the service group in each cluster.
