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.
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."
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:
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
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) ...
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.
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.