Is there any way using the API and/or powerShell to rerun a job? For example, let's say I have a backup job which was run with all the configurations via a scheduler, and it failed, I want to rerun it as is
↧
Rerun a Job
↧
Using data broker to mount VMs?
Hey,
Is there a way to use data broker to just mount a specific vm, meaning restoring it from a previous backup but without replacing the original one?
We have a corruption on one of our vms and we're not sure when it happened so that means restoring from the whole last week but I want to be able to bring up those VMs but without touching the original one.
I thought about just renaming and storage vmotion the original to a new datastore but if I restored it manually I could register the restored vm with a deifferent name while keeping the original.
Is that possible with data broker?
↧
↧
SnapCenter migration - does deleting the host delete the Exchange plug-in?
Hi,
We are migrating from one SnapCenter installation to a new one and have Exchange backups which have been recreated on the new environment and have been running successfully.
The question I have is that if we remove the Storage Systems from the old SnapCenter installation, will this automatically remove the Exchange plug-in and therby stop the recreated jobs from running on the new installation?
Thanks, Steven
↧
MongoDB ReplicaSet error SnapCenter Plugin
Hi,
We are attempting to use the SnapCenter MongoDB plugin to protect our MongoDB replica set VM instances running (VMware).
The replica set is made of the primary and 2 replicas. Each instance is provisioned its own VMware Datastore from an NetApp Ontap cluster, as follow:
1 Volume > 1 Lun > 1 Datastore > 1 mongod instance data
We followed the documentation provided with the Plugin, unfortunately few areas are not clear and we are running into some issues configuring our backups.
The SnapCenter configuration is as follow:
- Installed the Plugin on all 3 nodes of the Replica set
- Created 3 separate ReplicaSet Resources, one for each instance instance
- Created a Resource Group with all 3 ReplicaSets
We are getting the following error when running a backup, showing in the application Quiesce step:
SCC-00164: Application quiesce for plug-in [MongoDB] failed with exit code [1] and with error : File "/opt/NetApp/snapcenter/scc/plugins/native/MongoDB.py", line 35 except Exception, e: ^ SyntaxError: invalid syntax SCC-00161: Application unquiesce for plug-in [MongoDB] failed with exit code [1] and error : File "/opt/NetApp/snapcenter/scc/plugins/native/MongoDB.py", line 35 except Exception, e: ^ SyntaxError: invalid syntax SCC-00185: Cleanup for plug-in [MongoDB] failed with exit code [102] and error:
Do you have any pointers as to what to look for?
↧
Can't split clone for SQL backup on SnapCenter 4.3
Maybe I don’t understand something, but ... Does SnapCenter 4.3 support clone splitting for SQL databases resides on LUN?
When I try to split the clone I got the following error: "Failed to get the SMB server for storage system".
Which SMB server was looking for?
↧
↧
SnapManager for Exchange errors
hello all,
we found in the SnapManager logs the below errors that we need to iderstand its meaning so kindly help us:
Saving dataset backup metadata...
[23:06:00.465] SDDatasetBackupMetadataSet failed.
[23:06:00.465] [SDAPI Error]: DFM Zapi to start iteration to list Data sets failed. Error code: 13011. Error description: HTTP POST - Timed out.
102
[23:06:00.465] Unable to save dataset VSS backup metadata.
[23:06:00.465] [SDAPI Error]: DFM Zapi to start iteration to list Data sets failed. Error code: 13011. Error description: HTTP POST - Timed out.
102
[23:06:00.465] Starting dataset backup transfer now...
[23:06:00.465] Transfering now for dataset 'SnapMgr_Exchange_EXDRUEARTOP006' with retention type 'daily'...
[23:06:01.541] SDDatasetTransferNow failed.
[23:06:01.541] [SDAPI Error]: DFM Zapi to start iteration to list Data sets failed. Error code: 10061. Error description: Can't connect to host (err=10061)..
102
[23:06:01.541] Unable to perform dataset backup transfer now.
[23:06:01.541] [SDAPI Error]: DFM Zapi to start iteration to list Data sets failed. Error code: 10061. Error description: Can't connect to host (err=10061)..
[23:06:02.602] Backup of storage groups/databases successfully completed.
[23:06:02.602] However, archiving the backup to secondary storage failed.
[23:06:02.618] Unable to query autosupport settings.
[23:06:02.930] An autosupport message is sent to the storage system of LUN [E:\DATABASES\VDRTOP012MB1\VDRTOP012MB1.DB\]
↧
data broker backup at datastore cluster level feature
Hey,
Is it possible to ask the good fellas of the data broker team to consider adding a feature to backup at the vmware datastore cluster?
It will make life easier when adding new datastores (from netapp storage of course) and I don't think it's too much complicated for the data broker to query the vcenter using the api of what datastores compose it.
Thanks!
↧
Snapcentre NFS Discovery process
Hi guys,
Does anyone know how snapcentre discovers which SVM to use for NFS drives? It appears to scan every SVM and look at the export policies, thing is on this environment the same subnet exists at DC1/DC2 and DC3. As such when we perform a refresh any hosts on DC2 or DC3 are automatically selected for an SVM on DC1. DOH! We see LUN's just not NFS exports, I assume this is a limitation of the NFS discovery but I'm only making assumptions by trawling through the debug logs and drawing my own conclusions.
Here is what it looks like in the logs, as you can see a host in DC3 has been selected by snap centre to have its volumes in a SVM at DC1. This is a mistake of course, and I think it's due to the same subnet - if so snapcentre can't differentiate our sites and we either need to a) change the subnet b) deploy SC at each site or c) get help from NetApp to re-code so the selection process is more intelligent.
Here is the error:
We're running Snap Centre 4.3 on 2019 server and all the hosts (there are many) are on 2019 server. As such we tried this KB for fun (thinking it may do more than it suggests) but it hasnt helped.
:O
↧
Creating Clones of Snapcenter 4.3 Backups through Powershell
I am trying to use Powershell with Snapcenter 4.3 to create clones of the mirror copy of my backups. I am able to take the database backup and to clone the backup from the primary storage, but I am getting errors when trying to clone the backup.
This cmd successfully allows me to take a backup of one of my SQL databases which is spanned across 2 luns/vols:
New-SmBackup -ResourceGroupName LSB -Policy LiteSpeedLocal_MirrorClone
Then this will successfully create a clone of the backup on the primary SVM:
New-SmClone -BackupName "LSB_tst-sql_01-27-2020_14.59.47.9742" -Resources @{"host"="sqlclus-tst";"Type"="SQL Database";"Names"="TST-SQL\LiteSpeedLocal"} -AppPluginCode SMSQL -CloneToInstance "TST-SQL" -Suffix _PSClone -AutoAssignMountPoint
But if I try to point to the mirror copy it fails:
New-SmClone -BackupName "LSB_tst-sql_01-27-2020_14.59.47.9742" -Resources @{"host"="sqlclus-tst";"Type"="SQL Database";"Names"="TST-SQL\LiteSpeedLocal"} -AppPluginCode SMSQL -CloneToInstance "TST-SQL" -Suffix _PSCloneM -ArchivedLocators @{Primary="SVM1:tst_sql_sqlldf";Secondary="SVM2:tst_sql_sqlldf"} -AutoAssignMountPoint
Get-SmCloneReport
"Failed on 'sqlclus-tst-1':
Activity 'Discover Secondary Snapshot' failed with error: Archived locator match is not
found in discovered secondary snapshot locators. Please verify configured clone dataset
archived locators with secondary mirror or vault relationships. Clone Dataset Archived
Locator: SVM: SVM2, Volume: tst_sql_sqlldf < - > Discovered Secondary Locator:
SVM IRV-NC3-002, Volume: tst_sql_046047_sqlmdf"
I am using 2 LUNs/vols for this database as noted above, but the process succeeds when run on the primary storage (SVM1) but fails here when run on the snapmirror destination copy on SVM2 (SVM 2 is a on a different node using different aggr.)
↧
↧
SnapCreator 4.3.3P2 Checksums not matching on NetApp Support Site - error?
All,
Twice I've downloaded the SC 4.3.3P2 for Windows x64 and x32 and the packages don't match the checksums. I executed the installer and it appears to be running properly.
Can someone please check the md5 checksum values listed on the NSS SC download page are in fact, correct?
$ md5sum /var/tmp/NetApp_Snap_Creator_Framework4.3.3P2-Windows64.exe
30b1664104f2df6b7e7acd0a636471fa /var/tmp/NetApp_Snap_Creator_Framework4.3.3P2-Windows64.exe
$ cat checksums-Windows_x64.txt
.md5: 807c66e04ca12da814eb8d470d089b7e
↧
Help with Snapmirror error: Failed to create Snapshot (Invalid Argument)
Hi,
Having trouble with a snapmirror update not completing. It fails with the following error:
Failed to create Snapshot copy on volume [svm]:[volume] (Failed to create Snapshot copy on volume b079364c-3655-11e7-b5b9-00a09897da7d:[volume] (Invalid argument)
Can't seem to find any info as to what that means, and why it's happening.
Replication is happening between to different countries via VPN. I have about 7 volumes replicating. This is the only one that fails.
Any pointers?
Thanks.
↧
VSC 6.2.1 VMware 6.7
Hi Community,
i am running VSC 6.2.1 in a VMware 6.0 envirement. i plan to upgrade the VMware hosts to 6.7. is VSC 6.2.1 supporting VMware 6.7?
↧
snapshot plug in for Vertias NetBackup
We have installed our Veritas NetBackup server in NetApp storage with Redhat Linux, we are looking for a solution to replicate NetBackup to remote site as DR protection, which include NetBackup binary and catalog (SQL anywhere database) file systems. Since we don't have NetApp plug in for SQL anywhere, just wondering if we can utilize the plug in for Unix to protect our Linux file systems by replications. Please share your experience.
thanks
↧
↧
sdcli.exe Snapdrive replacement in Snapcenter
I want to use powershell for Snapcenter to clone backups of secondary storage, then add those clones to an igroup to present them as LUNs to dev/test servers, and then use PS again later dismount and delete the clones.
In Snapmanager/Snapdrive this could be done with sdcli disk connect/disconnect and Set-NaVol/RemoveNaVol. Does anyone here know the corresponding powershell cmds for Snapcenter?
↧
Backup MSSQL with snapcenter (migrate to Netapp Storage)
Trying out the MSSQL plugin for the first time but I have an issue.
Discovery works fine and all the databases come back ok but there is an error.
Not available for backup. DB is not on NetApp storage, auto-close is enabled or in recovery mode.
Its not autoclose or recovery so its obviously a storage issue.
Its a Vmware environment using NFS with all Vm's pretty much shared across a number of datastores.
What exactly has to be done to make Snapcenter happy, does the SQL logs and data have to be in a seperate NFS datastore or something along these line?
Cheers
↧
Snapcenter and Vmware question
Recently just installed snapcenter on a new vmware 6.7 poc environment.
I was able to get the VSC appliance up and running and get databroker to work to discover the vmware environment.
However once i have done that nothing actually shows in resources in Snapcenter to be able to view the vmware backups.
Is there something else I have to do to get this data visible?
The resource page only has a drop down for file systems and Ms SQL, i would expect to see a vmware one there?
Ty for assistance in advance
↧
NetApp custom plug in for Linux
can we use NetApp custom plug in for Linux around with Linux command "xfs_freeze" to replicate Linux file systems?
"xfs_freeze can freeze and resume the writing to the Linux file system.
thanks
↧
↧
I get error emial but snapshot is replicated to the destination netapp
Snapcenter 4.1.1.
After 3 month i get again the error for releationship.
but on Destination i see the snapsot. So everything should work . i only get a error mail.
I update Windows yesterday and now i have this E-Mail.
Replication failed for backup job 146923.
Status: Failed
Error:
SnapVault update failed for the relationship [netapp02-vm1 : datastore04 ==> netapp04-vm1 : datastore04_dst] with error: Snapshot copy 'RG_VM_SAP_Sandbox_02-25-2020_08.34.38.5346' not found on the SnapVault destination netapp04-vm1 : datastore04_dst
Backed up objects:
SmVMWareSANDataStore - datastore04ssd
↧
SnapCenter SQL - Restoring to a different database on the same server
Can someone just sanity check something for me?
We have a production SQL instance, and on that instance there is also a copy of a production database that we often use for training or testing. We regularly restore (currently using SQL backup and restore, but migrating to SnapCenter method) the production data from the "DCCI" database to the training "TRAIN" database. I just want to make sure that I have the steps right.
NB: We are currently using "Copy Only" SnapCenter backups because the old SQL backup routines are still running in parallel and handling log flushing and the like, so no need to restore any logs.
Here are my steps:
- Find the backup of the production database that I want to restore and start the restore procedure.
- Select the "Restore the database using existing database files" option, and choose the same server and instance, but enter the name of the database as "TRAIN" and enter the paths to the current mdf and ldf files for the TRAIN database.
- Check on the "Overwrite the database with the same name during restore" option on the Pre Ops screen.
- Start the restore.
Does this all sound right? I just want to have my ducks in a row before testing.
Thanks in advance,
Glenn
↧
SnapDrive Support?
I have not been able to find any official announcements from Netapp on the state of SnapDrive. It appears that SnapDrive is no longer listed as compatible with the newer version of ONTAP. Is the expectation that everything should be migrated to SnapCenter for the provisioning and administration of LUNs going forward?
We still have a number of servers with SnapDrive on them, and I'm wondering if I need to convert these over to SnapCenter. What's the process for doing this? Uninstall SnapDrive, then install SnapCenter? Vice versa? I can't find any guidance from Netapp on this.
↧