We are running ESX 4.1 and Avamar 5.0.3-29. We sometimes have image backups fail with error code 10007. This does not happen every night and happens with different vms running on different storage volumes. We backup about 150 vms a night and have 23 windows image proxies that handle those nightly backups. The error also occurs with different image proxies. The error code in the log is below:
2011-04-14 00:44:56 avvcbimage Info <5241>: Logging to /usr/local/avamar/var/Default Schedule-VM Images-1302757285296-74a05183c73ca62c88325e0f93464cb97341ec6f-3016-vmimage.log 2011-04-14 00:44:56 avvcbimage Info <5174>: - Reading /usr/local/avamar/var/avvcbimage.cmd 2011-04-14 00:44:56 avvcbimage Info <6636>: CTL listening on port 39978 2011-04-14 00:44:57 avvcbimage Info <5174>: - Reading /usr/local/avamar/var/avvcbimage.cmd 2011-04-14 00:44:57 avvcbimage Info <7045>: target[0]=[EqualLogic Group1 Volume 3] TG RC4ADOBE_2/ESX1_RC4ADOBE_TEST-New.vmdk 2011-04-14 00:44:57 avvcbimage Info <7045>: target[1]=[EqualLogic Group1 Volume 3] TG RC4ADOBE_2/ESX1_RC4ADOBE_TEST-New_1.vmdk 2011-04-14 00:44:57 avvcbimage Info <9642>: a VM snapshot has been requested 2011-04-14 00:45:02 avvcbimage Info <9645>: Requesting create snapshot progress from MC: query #1. 2011-04-14 00:45:13 avvcbimage Info <9645>: Requesting create snapshot progress from MC: query #2. 2011-04-14 00:45:24 avvcbimage Info <9645>: Requesting create snapshot progress from MC: query #3. 2011-04-14 00:45:34 avvcbimage Info <9645>: Requesting create snapshot progress from MC: query #4. 2011-04-14 00:45:35 avvcbimage Error <9647>: create snapshot failed with error:Another task is already in progress. on query #4 2011-04-14 00:45:35 avvcbimage Error <9709>: createSnapshot: snapshot creation failed 2011-04-14 00:45:35 avvcbimage Info <0000>: VixDiskLib: config options: libdir '/usr/lib/vmware', tmpDir '/tmp/vmware-root'.
2011-04-14 00:45:36 avvcbimage Info <0000>: VixDiskLib: Advanced transport plugin was successfully loaded into vixDiskLib. Accelerated transport modes available.
2011-04-14 00:45:36 avvcbimage Info <0000>: VixDiskLib: Enabling advanced transport modes.
2011-04-14 00:45:36 avvcbimage Info <0000>: VMware VixDiskLib (1.1) Release build-207031
2011-04-14 00:45:36 avvcbimage Info <0000>: Using system libcrypto, version 90807F
2011-04-14 00:45:36 avvcbimage Info <9616>: Available transport modes are file:san:hotadd:nbdssl:nbd 2011-04-14 00:45:36 avvcbimage Info <9617>: Calling ConnectEx with servername=192.168.0.107 vmxspec=moref=vm-367 on port 0 snapshot() 2011-04-14 00:45:36 avvcbimage Info <9618>: virtual machine will be connected readonly 2011-04-14 00:45:36 avvcbimage Info <9619>: VixDiskLib_ConnectEx returned VIX_OK 2011-04-14 00:45:36 avvcbimage Error <9720>: VixDiskLib_Connect(host:192.168.0.107 account:avamar dc:/SystemMetrics&dsName: vmxpath:[EqualLogic Group1 Volume 3] TG RC4ADOBE_2/ESX1_RC4ADOBE_TEST.vmx port:0vmmoref:vm-367) returned (0) The operation was successful 2011-04-14 00:45:36 avvcbimage Info <9723>: Final summary, cancelled/aborted 0, snapview 0, exitcode 0 2011-04-14 00:45:36 avvcbimage Info <0000>: UUID: SMBIOS UUID is reported as '42 18 19 bf 1c 1d 48 b7-b9 90 11 33 93 bb ff 71'.
I have same problem with different explanation. All of them has got the same ID number. Probably the same solution will fix this situation.
Does anybody has got an idea?
Error <9647>: create snapshot failed with error:File is larger than the maximum size supported by datastore ' on query #2
or;
Error <9647>: create snapshot failed with error:Another task is already in progress. on query #4
or;
Error <9647>: create snapshot failed with error:Virtual machine is configured to use a device that prevents the snapshot operation: Device '' is a SCSI controller engaged in bus-sharing. on query #1
or;
Error <9647>: create snapshot failed with error:Another task is already in progress. on query #4
We too have this issue, with only one or two clients. In one instance, it is left-over snapshot issue (not fully getting deleted). In another instance, some nights it works, some nights it does not.
El problema es que el DataStore donde reside la VM no tiene espacio suficiente disponible para hacer el snapshot.
Nosotros tuvimos el mismo problema y lo solucionamos haciendo el snapshot en un DS aparte creado específicamente para ello.
Para que esto suceda, necesitan:
1- Tener espacio suficiente en la caja de discos para crear una LUN lo suficientemente grande para albergar el snapshot.
2- Configurar cada VM para que el snapshot no lo haga sobre DS por defecto (generalmente en donde reside la VM), sino en el DS definido para ello.
Para cambiar el directorio por defecto donde se ubicaran los archivos de snapshots, seguir los pasos detallados a continuación:
1. Realizar un "Power off" de la máquina virtual.
2. Agregar la línea siguiente en el archivo de configuración de la máquina virtual (.vmx):
workingDir="
"
Por ej: workingDir="/vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots"
Nota: Alternativamente podemos especificar el path relativo por nombre de Datastore, por ej: Si el datastore donde queremos ubicar los snapshots se llama Snapshots_DS, la configuración debería ser: workingDir="/vmfs/volumes/Snapshots_DS/vm-snapshots"
3. Desregistrar la MV y volverla a registrar:
3.a: para desregistrar: botón derecho sobre la VM --> remove from inventory
3.b: para registrla nuevamente: Browserar el DS desde el ambiente vSphere, botón derecho sobre el archivo [VM].vmx --> add to inventory
4. Encender la MV.
Nota: Si se realiza un "storage vmotion", esta configuración se perderá, si es necesario esta configuración especial debemos realizar nuevamente el prociedimiento.
Hi,
The problem is that the datastore where the VM resides does not have enough space to make the snapshot. We had the same problem and solved by the snapshot in a separate DS created specifically for this purpose.
For this to happen, they need:
1 - Have enough space in the crate to create a LUN large enough to hold the snapshot.
2 - Configure each VM so that the snapshot does not do on DS by default (usually where the VM resides), but in the DS set for it.
To change the default directory where snapshot files are located, follow the steps below:
1. Perform "Power off virtual machine.
2. Add the following line in the file of virtual machine configuration (. Vmx):
workingdir = "
complete folder"
For example: workingdir = "/ vmfs/volumes/46f1225f-552b0069-e03b-00145e808070/vm-snapshots"
Note: Alternatively you can specify the relative path for Datastore name. For example: If the datastore where we want to locate snapshots called Snapshots_DS, configuration should be: workingdir = "/ vmfs / volumes / Snapshots_DS / vm-snapshots"
3. Unregister the VM and re-register:
3.a: To unregister: right click on the VM -> remove from inventory
3.b: To register again: the DS browser's vSphere from the environment, right click on the file [VM]. Vmx -> add to inventory
4. Turn on the MV.
Note: If you perform a "Storage VMotion", this setting will be lost if this special configuration we need to make prociedimiento again.
faltindal
1 Rookie
•
21 Posts
803
0
Posted May 20th, 2011 04:00
I have same problem with different explanation. All of them has got the same ID number. Probably the same solution will fix this situation.
Does anybody has got an idea?
Error <9647>: create snapshot failed with error:File is larger than the maximum size supported by datastore ' on query #2
or;
Error <9647>: create snapshot failed with error:Another task is already in progress. on query #4
or;
Error <9647>: create snapshot failed with error:Virtual machine is configured to use a device that prevents the snapshot operation: Device '' is a SCSI controller engaged in bus-sharing. on query #1
or;
Error <9647>: create snapshot failed with error:Another task is already in progress. on query #4
Thanks