Replies to This Discussion

Permalink Reply by Jerry Schmidt on April 27, 2015 at 7:06am

Hello Bill,

Suddenly receiving permission errors would suggest that something in the environment has changed.

The shares hosted by the synology NAS, are they CIFS or NFS?

If CIFS, did something with the active directory change? I typically check the NTP server first, you would want to make sure vmPRO, active directory, and the synology NAS all use the same NTP server as you will run into permission errors if the time difference between the devices is over 300 seconds.

• ▶ Reply

Permalink Reply by Bill Bajcz on April 27, 2015 at 7:12am

hello Jerry,

Thanks for the reply.  However, I do not believe this to be the problem as both devices use time.nist.gov as the ntp server and the units are within 3 or 4 seconds of each other.

Also, the share method in use is NFS.

• ▶ Reply

Permalink Reply by Jerry Schmidt on April 27, 2015 at 7:23am

Does the issue happen with all the VMs you are trying to backup up or with just a single VM?

You could attempt to rediscover the VM or VMs.

Using the vmPRO GUI, go to the VM tab, then on either the VM or the folder that the VMs reside in, select, then disable export and CBT.

Next reboot the vmPRO node.

Once it is back online, select the VM or the folder the VMs reside in and enable export and CBT, you should see snapshots being created and removed on the VMs from vSphere when CBT is enabled.

Try running a backup again.

• ▶ Reply

Permalink Reply by Bill Bajcz on April 27, 2015 at 7:45am

No change, same error.

I have created and downloaded a "support package".  Would this be helpful in any way?

• ▶ Reply

Permalink Reply by Jerry Schmidt on April 27, 2015 at 8:27am

It should help, if possible use the Upload Files feature on the forum and upload the support bundle.

• ▶ Reply

Permalink Reply by Bill Bajcz on April 27, 2015 at 8:29am

Ok,

Here it is

Attachments:

• toledo-pancetera-support.tar.bz2, 5.7 MB

• ▶ Reply

Permalink Reply by Jerry Schmidt on April 27, 2015 at 8:51am

So vmPRO is able to run a storage test write, lock and unlock the target storage, but when it attempts to push data to the target storage we receive the permission error because vmPRO is not allowed to create a new folder on the target storage.

Did the permissions on the NFS share get changed to read only?

2015-04-27 07:42:45,153 smartmotion/ERROR:: ControllerCommands.py:3296 SmartMotion backup failed
Traceback (most recent call last):
  File "/usr/local/pancetera/python/controller/ControllerCommands.py", line 3289, in do_tomato_sync_folder
    t.run_sync_now(c, queued_time, sm_uuid, vm_folder_uuid, arg_policy, smtask)
  File "/usr/local/pancetera/python/controller/Tomato.py", line 2275, in run_sync_now
    self._tomato_create_sync_folder(target_folder)
  File "/usr/local/pancetera/python/controller/Tomato.py", line 912, in _tomato_create_sync_folder
    os.makedirs(new_folder)
  File "/usr/lib64/python2.6/os.py", line 157, in makedirs
    mkdir(name, mode)
OSError: [Errno 13] Permission denied: '/storage/.e02c4acf-13f3-40fa-84ef-58d4c5985458/2015-04/2015-04-27-074243'

If there have been no changes to the NFS share, then from the vmPRO GUI, pull up the configuration wizard and go to the storage tab. Deleted the share and then re-add the share. Try running the backup again. Maybe we have a stale NFS mount.

If the backups fail again, try creating a new share on the synology NAS and point vmPRO to use that share for target storage. Try running a backup again. If the backup runs then something has changed on the original share and that change is not allowing vmPRO to create folders on the share.

• ▶ Reply

Permalink Reply by Bill Bajcz on April 27, 2015 at 1:22pm

The new target worked.

Thank you.

• ▶ Reply