At work we use vRanger to take DR snapshots of all our VM’s (more than 400).<\/p>\n
We decided that we would only snapshot drive 0 and use a TSM client to backup the data in each VM and that the snapshots were only to be taken outside working hours.
\nThese choices gave us some problems when running vRanger because we couldn’t schedule the snapshots from vRanger.<\/p>\n
Because we have more than 400 VM\u00e2\u20ac\u2122s we had to divide the list of witch VM\u00e2\u20ac\u2122s to backup, into 14 days.
\nThis means that one specific VM will only be snapshotted every 2 weeks.<\/p>\n
In Virtual Center we created a custom field (=Backup) to tell the script witch VM’s to snapshot witch days.
\nWe use full weekdays together with Even \/ Odd for dividing the VM’s into 14 days.
\nEx. “Monday-Even” or “Sunday-Odd”
\n![\"\"](\"http:\/\/www.amikkelsen.com\/images\/vc_backup.jpg\")
<\/p>\n
The solution was to make our own script that would handle the logic and just use vRanger to do the actual snapshotting.
\nWe created a VBS script to hold the logic.
\n1.
\nCreate a log file
\n2.
\nDelete snapshots from the day before (due to lack of storage space on the server)
\n3.
\nGenerate the .cmd file from information in a custom field (Backup) in VC
\n4.
\nCall the .cmd file that was created earlier and contains the information on which VM’s to snapshot (Based on weekday – one file for each day).
\n5.
\nStart TSM (send the VM’s snapshots to tape)
\n6.
\nSend a status mail<\/p>\n
(You have to use vRanger GUI to choose which drives to snapshot – changed from 3.17 -> 3.20)<\/p>\n
I know this solution isn’t very dynamic but i works.<\/p>\n
You can download the new script here<\/a> \u00e2\u20ac\u201c version 2.0.<\/p>\n","protected":false},"excerpt":{"rendered":" I\u00e2\u20ac\u2122m now done with the new script and it\u00e2\u20ac\u2122s working perfectly. Background for the script: At work we use vRanger to take DR snapshots of all our VM’s (more than 400). We decided that we would only snapshot drive 0 and use a TSM client to backup the data in each VM and that the\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,4,18],"tags":[],"class_list":["post-74","post","type-post","status-publish","format-standard","hentry","category-disaster-recovery","category-scripting","category-vranger"],"_links":{"self":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/posts\/74","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=74"}],"version-history":[{"count":1,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/posts\/74\/revisions"}],"predecessor-version":[{"id":309,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/posts\/74\/revisions\/309"}],"wp:attachment":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=74"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=74"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}