
Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
F
frank_grimes
5 Posts
0
1583
July 3rd, 2017 07:00
Networker 9.1 vProxy & Directives
We're looking to implement NW 9.1.1 in a highly virtualized (VMware) SQL environment and I would like to move towards image-based backups. I realize that not everything should be snapped and we will identify the servers that have high transaction rates, but one of my main concerns is obviously impacting database performance.
In the past, I used a different backup product and was able to filter out all datastores that contained the .ldf, .mdf, and .ndf files, leaving only the C: drive and maybe a utility drive or two to be backed up. I then had a SQL agent installed to backup the database and logs separately. This worked out great because I could now avoid database stuns during the snapshot operation and not have to backup all of the data essentially twice in a night.
So, is there a way to filter out specific datastores, vmdk's, or hard disks using directives? Or am I going to have to go into the Group and drill down into every VM then manually deselect drives that I do not want snapped?
Responses (1)
Solutions (0)

AdiYogi_b4c4fd
15 Posts
620
0
Posted July 6th, 2017 05:00
our compute engineer planned to place the SQL db files in drives other than C and D which were holding Os and SQL installation files respectively. we are excluding the VMDK in the vproxy backups by expanding the VM
while restoring we may see some issue if we try restoring all VMDKs, the same error will not be seen if we restore the VMDKs that we backedup or included