SC 3.4.0 and MySQL 5.0.x Windows Server 2008 R2 within VMware virtual machine [ Edited ]

[#1]

Hello.  I understand that the Interoperability Matrix Tool does not show SC 3.4.0 and MySQL 5.0.x as compatible.  However, I want to try to manually use the mysql command as suggested here <http://communities.netapp.com/message/48366#48366>.  In this case a physical Windows Server 2008 R2 server is running the SC server (which also happens to be a VMware vCenter 4.x host) that will be issuing commands to a VMware virtual Windows Server 2008 R2 agent where the MySQL databases reside.  As I am learning how SnapCreator works - I'm not sure where I need to set the manual commands.

Additionally, as I understand it, I need to setup "New Configuration" with Advanced Options? and then select VMware vSphere and select "VM + Application consistent" to cover provide a consist virtual machine snapshot as well as the MySQL database hosted within.

Thank you.

compatible

[#2]

One more item - SMVI is being used in this environment and I am trying to understand if a single VM is selected within a VMFS datastore if that will result in other VMs on that datastore being snapped.  If that is the case,reviewing SMVI's schedule of snaps may be needed.  The 3.4.0 SC documentation notes, "If a Datastore is listed, all the VMs in the Datastore will be backed up."

Thank you.

[#3]

Dont do the vm + app that is for backing up vm and app in this case mysql together. The only reason you would do that is if you wernt using rdm or nfs for mysql.

SC basically creates a few configs and builds workflow to quiesce mysql, take vmware snap, netapp snap, remove vmware snap, unquiesce mysql. Since you have smvi you dont need SC to deal w/VM.

I recommend you do following:

1. Try mysql plugin even though it isnt in imt, it may still work

If it doesnt then simply sekect application none

Then after creating config you can edit it and enter app quiesce cmds, app unquiesce cmds, and pre exit cmds. You could also edit config by hand.

APP_QUIESCE_CMD01=<cmd to quiesce mysql>

APP_UNQUIESC_CMD01=<cmd to unquiesce mysql>

PRE_EXIT_CMD01=<cmd to unquiesce mysql>

If you are using these cmds dont forget to add them to scAgent if your using agent under config/agent.conf

Also make sure APP_NAME is commented out or not set if you want to do cmds yourself

Please read other community posts there is more info in other threads that will help you

Good Luck

Keith

[#4]

Just to be clear on one point with SC vs SMVI

If your using SMVI you would just use it for backing up VMs and SC for backing up applications like mysql or even other SnapManagers.

SC is not a SnapManager, its a lightweight backup/restore framework for netapp. You could do everything w/SC including backup vms but a SnapManager will provide more features for a given app. What SC provides is a single toolkit to design your own solutions. So its great for custimizing or integration into existing tools, even to accomplish singke pane of glass for backup but it is providing quite different solutions than a SnapManager and visa versa.

Hope this helps

Keith

[#5]

Thank you for the helpful replies.  The VM is not using RDM or NFS for MySQL so VM + APP is needed.  I will continue to work on the setup.  Thanks.

[#6]

Got it, then I woukd just backup VM w/mysql so SC doesnt conflict w/smvi.

Also you will need scAgent running inside VM to handle mysql part of backup

Keith

[#7]

SC server and agent are on the physical vCenter server.  SC agent is installed on the VM that hosts MySQL.  SC has been setup with VM + APP.  This created are 5 configurations under one backup profile (hostname, hostname_mysql_1, hostname_mysql_2, hostname_restore, hostname_vibe).  Due to the GUI scheduling issue noted here <http://communities.netapp.com/thread/15842?tstart=0>, I want to create a batch script to be kicked off by the Windows Scheduler.  It seems that his should be a one line batch script:

D:\Program Files\NetApp\NetApp_Snap_Creator_Framework\scServer3.4.0>snapcreator.exe --profile HOSTNAME --action snap --policy hourly --config_dir "D:\Program Files\NetApp\NetApp_Snap_Creator_Framework\scServer3.4.0\configs\VMware MySQL snap”

It appears that there is no output or action so added “--debug”  and “--verbose”.

########## APPLICATION QUIESCE COMMANDS ##########

[Mon Jul 18 11:44:50 2011] INFO: Running application quiesce command APP_QUIESCE_CMD01 ["D:/Program Files/Netapp/NetApp_Snap_Creator_Framework/scServer3.4.0/snapcreator.exe" --profile VMware MySQL snap --config HOSTNAME_mysql_1 --action quiesce]

[Mon Jul 18 11:44:50 2011] DEBUG: Executing command ["D:/Program Files/Netapp/NetApp_Snap_Creator_Framework/scServer3.4.0/snapcreator.exe" --profile VMware MySQL snap --config HOSTNAME_mysql_1 --action quiesce]

[Mon Jul 18 11:44:51 2011] DEBUG: Command ["D:/Program Files/Netapp/NetApp_Snap_Creator_Framework/scServer3.4.0/snapcreator.exe" --profile VMware MySQL snap --config HOSTNAME_mysql_1 --action quiesce] finished with

exit code: [256]

stdout: [ERROR: [scf-00037] Missing Required option --action

The error states it is missing the –action parameter but it appears to be there?

Any thoughts as to what may be missing here?

Thank you.

[#8]

SC for vm + app creates 4 configs

1 master config this is name of the profile and config you should be running

1 VMware config file, this is for quiesce/unquiesce of VM

1 MySQL config file, this is for quiesce/unquiesce of MySQL

1 Config to use for restores, we would restore VM and then you would need to roll MySQL forward or bring DB online (it would be in a read-only state).

When looking at this command there is a pace in profile name "VMware MySQL". We cannot handle this, actually the GUI shouldnt allow it but I guess it isnt checking. I would re-create config with no spaces.

To troubleshoot you are right your master config, the profile name wont have too many details about VM or MySQL. For info on why they worked or didnt you will see a log and you need to look at those logs. Each config creates different logs.

D:/Program Files/Netapp/NetApp_Snap_Creator_Framework/scServer3.4.0/snapcreator.exe" --profile VMware MySQL snap --config HOSTNAME_mysql_1 --action quiesce

Hope this helps

Keith

[#9]

Thank you Keith.  Getting closer here.  Removed the spaces from the profile name and that resolved that issue (the GUI does not flag space as an issue).

Discovered the MySQL plugin only sets custom port as specified in the GUI for the first DB in defined - the remaining defaults to 3306.  Corrected this in the in the HOSTNAME_mysql_1.conf config file manually.

New issue - VMware snapshot issue:

[Mon Jul 18 13:35:00 2011] DEBUG: Collecting LUN information ...

[Mon Jul 18 13:35:00 2011] DEBUG: Attempting to collect LUN serial numbers for storage appliance 192.168.150.41 ...

[Mon Jul 18 13:35:00 2011] DEBUG: Searching for matching disk name naa.60a98000534b4e73476f634957342f68 on storage appliance(s) ...

[Mon Jul 18 13:35:02 2011] DEBUG: Checking host system prtesx3 ...

[Mon Jul 18 13:35:02 2011] DEBUG: Name = naa.60a98000534b4e73476f634957342f68, UUID = 534b4e73476f634957342f68.

[Mon Jul 18 13:35:02 2011] DEBUG: Found LUN with UUID 534b4e73476f634957342f68,host 192.168.150.41, path /vol/VMFS1/VMFS1.

[Mon Jul 18 13:35:02 2011] INFO: Collecting VM information on VMFS Datastore NetApp_VMFS_01.

[Mon Jul 18 13:35:02 2011] DEBUG: Searching for Datastore NetApp_VMFS_04 ...

[Mon Jul 18 13:35:02 2011] DEBUG: Requested Datastore (NetApp_VMFS_04) is available.

[Mon Jul 18 13:35:02 2011] DEBUG: Searching for matching disk name naa.60a98000534b4e71674a636a3834334f on storage appliance(s) ...

[Mon Jul 18 13:35:04 2011] DEBUG: Checking host system prtesx3 ...

[Mon Jul 18 13:35:04 2011] DEBUG: Name = naa.60a98000534b4e73476f634957342f68, UUID = 534b4e73476f634957342f68.

[Mon Jul 18 13:35:04 2011] DEBUG: Name = naa.60a98000534b4e73476f636142333155, UUID = 534b4e73476f636142333155.

[Mon Jul 18 13:35:04 2011] DEBUG: Name = naa.60a98000534b4e71674a634957463375, UUID = 534b4e71674a634957463375.

[Mon Jul 18 13:35:04 2011] DEBUG: Name = naa.60a98000534b4e71674a636a3834334f, UUID = 534b4e71674a636a3834334f.

[Mon Jul 18 13:35:04 2011] ERROR: [vmw-00006] Could not find identifying LUN on any storage appliance for VMFS datastore!

It appears that VIBE cannot find the LUN.

Thank you.

[#10]

Hi, all.  Can you please send over (private message is fine) the configuration file parameters as well as the full debug log?  It generally can't find the LUN as the storage controller doesn't show the matching UUID (it does find the name, it looks like) in the list of local LUNs.  I'm curious to see what the VOLUMES value is set to (after discovery) or if this has never run, what the full log looks like.

It looks like prtesx3 (one of the hosts discovered) either doesn't have NetApp_VMFS_04 mounted as a datastore or the path doesn't show up with the same UUID.

Thanks,

--Matt